IO domain DNS failure

#1

Post by yoshiokatsuneo » Fri, Oct 28, 2016, 4:21 AM UTC

For 3 or 4 hours, IO domain DNS lookup often fails. Now, only 2 out of 7 IO domain nameservers respond, and other 5 DNS nameservers are dead.

Re: IO domain DNS failure

#2

Post by a10c » Fri, Oct 28, 2016, 4:34 AM UTC

I have been seeing the same failures for many IO TLDs

I have noticed the failures occurring moreso in Asia and Russia than in other regions.

#3

Post by yoshiokatsuneo » Fri, Oct 28, 2016, 4:39 AM UTC

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.

#4

Post by asher_ » Fri, Oct 28, 2016, 5:52 AM UTC

We are experiencing the same from Vietnam

#5

Post by mic159 » Fri, Oct 28, 2016, 6:14 AM UTC

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

#6

Post by tkazec » Fri, Oct 28, 2016, 6:29 AM UTC

We've been seeing this for exactly five hours now, all across East Asia.

Edit: Looks like .io is managed in London, and their customer service off hours match the downtime.

#7

Post by user9999 » Fri, Oct 28, 2016, 6:38 AM UTC

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

#8

Post by yoshiokatsuneo » Fri, Oct 28, 2016, 7:08 AM UTC

So, "ns-a4.io" is the culprit! On ns-a4.io, xxx.io can be resolved, but yyy.xxx.io cannot be resolved(delegated). Ref: http://qiita.com/MasahitoShinoda/items/40cd312fabc6db604b39

#9

Post by yjchang » Fri, Oct 28, 2016, 7:56 AM UTC

Same here in South Korea. Still not fixed.

#10

Post by xiaodown » Fri, Oct 28, 2016, 8:51 AM UTC

Getting significantly worse now.