IO name servers down

#1

Post by gator-io » Wed, Sep 20, 2017, 2:04 PM UTC

I'm getting swamped DNS resolution errors for anything .IO.

ns-a1.io timesout on every request so do all the others

Re: IO name servers down

#2

Post by [deleted] » Wed, Sep 20, 2017, 2:08 PM UTC

[deleted]

Re: IO name servers down

#3

Post by nodesocket » Wed, Sep 20, 2017, 2:09 PM UTC

Same here for my startup commando.io. Using AWS Route53. What DNS provider are you using?

Re: IO name servers down

#4

Post by turdnagel » Wed, Sep 20, 2017, 2:10 PM UTC

nodesocket wrote: post #3

Same here for my startup commando.io. Using AWS Route53. What DNS provider are you using?

Same here, also using Route 53.

Re: IO name servers down

#5

Post by tbarbugli » Wed, Sep 20, 2017, 2:12 PM UTC

These two nameservers: ns-a2.io, ns-a4.io return wrong results consistently

Re: IO name servers down

#6

Post by nodesocket » Wed, Sep 20, 2017, 2:13 PM UTC

turdnagel wrote: post #4

nodesocket wrote: post #3

Same here for my startup commando.io. Using AWS Route53. What DNS provider are you using?

Same here, also using Route 53.

I was certain I was getting DDoS'd, but then I inspected the Pingdom down notifications and seeing: DNS error

Re: IO name servers down

#7

Post by tbarbugli » Wed, Sep 20, 2017, 2:13 PM UTC

team mate posted on HN already about this: https://news.ycombinator.com/item?id=15293578

Re: IO name servers down

#8

Post by cjsuk » Wed, Sep 20, 2017, 2:19 PM UTC

nodesocket wrote: post #6

turdnagel wrote: post #4

Earlier quoted context omitted.

Same here, also using Route 53.

I was certain I was getting DDoS'd, but then I inspected the Pingdom down notifications and seeing: DNS error

Same here on Route53.

Re: IO name servers down

#9

Post by dastbe » Wed, Sep 20, 2017, 3:51 PM UTC

nodesocket wrote: post #3

Same here for my startup commando.io. Using AWS Route53. What DNS provider are you using?

From the AWS status page:

"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."

Re: IO name servers down

#10

Post by devnull42 » Wed, Sep 20, 2017, 3:56 PM UTC

It appears that the issue at first impacted all servers in the anycast pool however eventually it only impacted servers ns-a2 and ns-a4. Those servers started returning NXDOMAINs. I am wondering if this was related to the root server key change yesterday. .IO seems to struggle with basic DNS engineering. We are seeing stabilization except for minor issues still on one of the gTLD servers.