http://scotch.io
http://codemonkey.io
http://geocod.io<p>Are all down for me.<p>$ host filepicker.io
Host filepicker.io not found: 3(NXDOMAIN)
There are some things you can do to protect yourself against these kinds of problem. About 92% of DNS resolvers honour the TTL setting for the NS records from the leaf-node child-zones (e.g. the NS records you control as the owner of a domain). If your domain is reasonably popular, then that caching can help you outlast a problem with your TLDs name-servers. 2 days is a pretty common number for a cache lifetime.<p>Unfortunately for the 8% of resolvers that honour the TTL in the parent domain, you have less control. In this case for .io, the parent-zone NS ttls are just one hour;<p><pre><code> ;; AUTHORITY SECTION:
nic.io. 3600 IN NS ns1.communitydns.net.
nic.io. 3600 IN NS b.nic.ac.
nic.io. 3600 IN NS a.nic.io.
nic.io. 3600 IN NS b.nic.sh.
nic.io. 3600 IN NS ns4.nic.io.
nic.io. 3600 IN NS dns01.cdns.net.
nic.io. 3600 IN NS b.nic.io.
</code></pre>
which I think is relatively short by TLD standards.<p>Another important thing to consider is that the TLD you choose for your domain itself isn't the only TLD that your domain resolution may depend upon. Resolution also depends on all of the domains of your nameservers resolving too. Route 53 assigns every hosted zone 4 nameservers from 4 different TLDs, e.g.;<p><pre><code> example.info. 172800 IN NS ns-1834.awsdns-37.co.uk.
example.info. 172800 IN NS ns-22.awsdns-02.com.
example.info. 172800 IN NS ns-912.awsdns-50.net.
example.info. 172800 IN NS ns-1233.awsdns-26.org.
</code></pre>
So that if any one of those TLDs has a problem it does not cause a resolution failure for your zone. Some other providers do this too, and it's also something you could set up yourself.<p>Full-disclosure: Route 53 engineer here.
Anthony from DNSimple here. I'll pass along what I know so far: some of nic.io's name servers appear to be no longer delegating .io domains out to authoritative name servers. Some of their name servers are still delegating properly, but some are not.<p>This issue also affects .sh and .ac TLDs I believe since they are the same registry. If I find out anything new I'll post on Twitter in the @dnsimple account and here.
We're back online at <a href="http://candid.io" rel="nofollow">http://candid.io</a>. Someone on twitter posted "VCs should think twice before investing in startups without a .com" -> I think that's patently absurd. Azure, AWS, and the other 'core infrastructure' services suffer similar outages form time to time.
They have 7 name servers, 5 are broken and returning NXDOMAIN for all domains.<p>Working:<p>b.nic.io.
ns1.communitydns.net.<p>Not working:<p>a.nic.io.
a.ns13.net.
b.nic.ac.
b.ns13.net.
ns3.icb.co.uk.
Wow. About a year ago the the entire .st registry went down for about 8 hours:<p><a href="http://blorn.com/post/29851770158/beware-cutesy-two-letter-tlds-for-your-domain-name" rel="nofollow">http://blorn.com/post/29851770158/beware-cutesy-two-letter-t...</a><p>I guess the title of the blog post pretty much says it all.
On April 29 I received a notice from admin@nic.io concerning user-generated content that I was to remove from an IO domain "by April 2" (ie a month earlier) - otherwise they would advise the complaintant to contact law enforcement and would suspend the domain "upon receipt of a formal request to do so".
When I attempted to reply, the email address was out of order ("Write error: Broken pipe") and remained so for several days.<p>It doesn't seem to be the most professionally run domain...
My site <a href="http://gitignore.io" rel="nofollow">http://gitignore.io</a> was down and I just pinged my CDN and my domain host to see what the problem was. Everything seems to be back up and running now. Does anyone know what happened?
Check out <a href="http://www.whatsmydns.net" rel="nofollow">http://www.whatsmydns.net</a> pretty useful for seeing where issues are or tracking propagation.
I experienced this as well at <a href="http://quantify.io" rel="nofollow">http://quantify.io</a> - New Relic reported a 2 hour outage which just ended.
Yes! My site (robert.io) is down and I've been chasing my tail trying to figure out what's wrong. It's refreshing to see that I'm not the only one.
For me too.. well, sometimes it resolves, sometimes it doesn't. There seems to be an issue with .io globally: <a href="https://twitter.com/dnsimple/status/342991722365734912" rel="nofollow">https://twitter.com/dnsimple/status/342991722365734912</a>
We had this happen before to our .st domain. <a href="http://blorn.com/post/29851770158/beware-cutesy-two-letter-tlds-for-your-domain-name" rel="nofollow">http://blorn.com/post/29851770158/beware-cutesy-two-letter-t...</a>
Pingdom reckons <a href="https://www.photographer.io" rel="nofollow">https://www.photographer.io</a> is still up, but I guess I really can't be certain. It hasn't been a great week for my domain, what with the DNSimple attack and this.
Intercom.io is down as well. Particularly frustrating since its preventing me from replying to customer emails.<p>Technical details of permanent delivery failure: DNS Error: Domain name not found
In some sort of irony, statuspage.io is down. Was looking at their offering about an hour ago and thinking of taking it for a spin, but now I'm not so sure...
you can check whatsmydns.net, how some places are working, and some not, for example: <a href="http://www.whatsmydns.net/#A/www.works.io" rel="nofollow">http://www.whatsmydns.net/#A/www.works.io</a>
from Germany a.ns13.net and b.ns13.net return NXDOMAIN. Both seem to be located in JP. The other DNS are working for me.<p>They recently switched their backend to a new platform (May 29th) maybe this issue is related…