IO domain DNS failure

AWS response:<p>Hello,<p>Some customers have reported intermittent resolution issues with .io domains. We can confirm that Route 53 DNS services are operating normally at this time and these issues seem to be related to the .io top-level domain provider.<p>We&#x27;ve investigated the issue and are primarily seeing incorrect responses from two of the .io nameservers: ns-a4.io and ns-a2.io. These nameservers are returning NXDOMAIN intermittently for domains that do exist. As a result, once a resolver receives the erroneous response, it will cache the non-existence for the negative TTL, which for .io is set to 3600 seconds (1 hour).<p>One suggestion we have is to increase the TTLs for your domains in Route 53 so that the resolvers cache DNS answers for a longer duration.<p>Best regards,<p>(Customer support rep name redacted)<p>Amazon Web Services<p>We value your feedback. Please rate my response using the link below.

I recieved this reply from nic.io support a few minutes ago: <a href="http:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;wV2Kk" rel="nofollow">http:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;wV2Kk</a>

I have been seeing the same failures for many IO TLDs<p><a href="https:&#x2F;&#x2F;www.whatsmydns.net&#x2F;#A&#x2F;gitlab.io" rel="nofollow">https:&#x2F;&#x2F;www.whatsmydns.net&#x2F;#A&#x2F;gitlab.io</a><p>Example: <a href="https:&#x2F;&#x2F;i.imgur.com&#x2F;SU4BAHK.png" rel="nofollow">https:&#x2F;&#x2F;i.imgur.com&#x2F;SU4BAHK.png</a><p>I have noticed the failures occurring moreso in Asia and Russia than in other regions.

So, &quot;ns-a4.io&quot; is the culprit! On ns-a4.io, xxx.io can be resolved, but yyy.xxx.io cannot be resolved(delegated). Ref: <a href="http:&#x2F;&#x2F;qiita.com&#x2F;MasahitoShinoda&#x2F;items&#x2F;40cd312fabc6db604b39" rel="nofollow">http:&#x2F;&#x2F;qiita.com&#x2F;MasahitoShinoda&#x2F;items&#x2F;40cd312fabc6db604b39</a>

We are also having issues resolving some .io domains from AWS Sydney (ap-southeast-2)

For those interested, we wrote a blog post about single points of failure with DNS last Friday when the Dyn attack happened. Our strategy ensures our customers are mostly unaffected by issues like this. See <a href="https:&#x2F;&#x2F;blog.ably.io&#x2F;routing-around-single-point-of-failure-dns-issues-7c20a8757903" rel="nofollow">https:&#x2F;&#x2F;blog.ably.io&#x2F;routing-around-single-point-of-failure-...</a>

There are 7 IO nameservers (ns-d1.io, ns-l1.io ,ns-y1.io, ns-a1.io, ns-a2.io, ns-a3.io). Only ns-a4.io and ns-a3.io respond.

It looks, the the problematic nameserver &quot;ns-a4.io&quot; is down. So, the problem should be disappeared...<p>At the same time, it looks, there is only one &quot;ns-a3.io&quot; nameserver working for IO domain, at now...

For Planio (<a href="https:&#x2F;&#x2F;plan.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;plan.io&#x2F;</a>), all accounts are available via yourname.planio.net as an alternative while this outage lasts.

We&#x27;ve been seeing this for exactly five hours now, all across East Asia.<p>Edit: Looks like .io is managed in London, and their customer service off hours match the downtime.

Two of their servers were sending out NXDOMAINs which are then cached by downstream forwarders. It seems they have turned those off now.

This is still affecting us. Our customers on Heroku seem to be the worst affected as Heroku is unable to resolve the DNS

We are experiencing the same from Vietnam

.sh and .ac are also run by the same folks - looks like there are issues with those tlds as well.

Having the same issue in Singapore. got nothing to do, helpless.

Same here in South Korea. Still not fixed.

Getting significantly worse now.