Some .io nameservers are returning wrong results again

I Contacted Cloudflare and the response was:<p>&quot;Unfortunately this stops DNS traffic before it gets to Cloudflare so it is not a problem we can solve for you as much as we would love to. Our recommendation right now would be to contact your domain registrar to understand more about this problem.&quot;<p>Contacted the registrar (iwantmyname.com) and their response:<p>&quot;You&#x27;re using external CloudFlare hosting, so our DNS management isn&#x27;t being used. We don&#x27;t have any access to the hosting account or the ability to address issues there. It does appear there&#x27;s some issue with propagation.&quot;

If you DNSSEC sign your domain then the NXDOMAIN would be rejected without associated NSEC records. .io has a DS record in the root-zone. At the very least caches would only be populated with the correct answer.<p>This is of course assuming the lookups are done using a validating resolver.

We&#x27;re copping the same at <a href="https:&#x2F;&#x2F;elev.io" rel="nofollow">https:&#x2F;&#x2F;elev.io</a> as well...<p>Timing couldn&#x27;t be worse, we did a product release on ProductHunt earlier today :(

Afilias manages the .io domain. Give them a call: +1 866.368.4636 <a href="https:&#x2F;&#x2F;afilias.info&#x2F;contact-us&#x2F;support" rel="nofollow">https:&#x2F;&#x2F;afilias.info&#x2F;contact-us&#x2F;support</a>

.io seems to always have problems. its really sad that lots of people use this domain because it looks cool :( [at work we use this as well]

If this is affecting you it&#x27;s best to put a long TTL (at least 1 hour) on your domains. That way a good lookup will be cached longer and it will affect less people.

Confirmed ns-a2.io and ns-a4.io don&#x27;t seem to be responding with DNS results.

Customers are already filling up our support inbox, so same here. They can access nic.io<p>Any quick fix ideas I can get to a customer without technical command-line experience? Changing DNS or modifying hosts file is not really an option.

The nameservers seem to be returning correct results for our domain again :) (getstream.io). However, the issue is still there for crates.io, so this seems the outage is still partially ongoing.

Indeed I noticed the same issue for my customers using .io domains (and me unfortunately): <a href="https:&#x2F;&#x2F;twitter.com&#x2F;updownio&#x2F;status&#x2F;910508435720065024" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;updownio&#x2F;status&#x2F;910508435720065024</a><p>Seems to be getting better now. High TTL helps but mostly if it was there before so do it now for the next downtime (it&#x27;s frequent with .io)

We&#x27;re seeing this as well.<p>Edit: it has now taken out our CI infrastructure and dev environments as it&#x27;s caching NXDOMAIN records.

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.

I guess that&#x27;s just the cost of business when your start up is located in the British Indian Ocean Territory

I wonder if they messed up again and let someone register the .io nameservers<p><a href="https:&#x2F;&#x2F;thehackerblog.com&#x2F;the-io-error-taking-control-of-all-io-domains-with-a-targeted-registration&#x2F;" rel="nofollow">https:&#x2F;&#x2F;thehackerblog.com&#x2F;the-io-error-taking-control-of-all...</a>

Wanted to confirm same issue for my .io domains. This has gotten a lot of people up this morning.

For the curious, the first failure I saw was at 13:15UTC and the last was 14:59UTC.

Same issue here. Does NIC.io have a status page for their root servers somewhere?

We are getting some client reports of connectivity issues with clara.io. I suspect it is this issue but haven&#x27;t been able to confirm.

IO apears to have nameservers operated by Afilias, CommunityDNS, OneWorld DNS (which appear to also be CommunityDNS)<p><pre><code> $ for ns in $(dig +short io. IN NS | sort); do ip=$(dig +short ${ns} IN A); rev=$(host ${ip} | awk -Fpointer &#x27;{print $2}&#x27;); echo -n &quot;= $ns = $ip = $rev = &quot;; whois -h whois.ripe.net ${ip} | awk -F: &#x27;&#x2F;^descr:&#x2F; &amp;&amp; !&#x2F;RIPE&#x2F; {print $2}&#x27;; done = a0.nic.io. = 65.22.160.17 = a0.nic.payu. = Afilias NS087 A0 = b0.nic.io. = 65.22.161.17 = b0.nic.payu. = Afilias NS087 B0 = c0.nic.io. = 65.22.162.17 = c0.nic.payu. = Afilias NS087 C0 = ns-a1.io. = 194.0.1.1 = ns1.communitydns.net. = ICB plc Anycast (via NetConnex AS21396), ICB plc Anycast (via Community DNS AS42909) = ns-a2.io. = 194.0.2.1 = ns-a2.io. = ICB plc Anycast (via Community DNS AS42909) = ns-a3.io. = 74.116.178.1 = b3-1.oneworlddns.net. = Community DNS = ns-a4.io. = 74.116.179.1 = b4-1.oneworlddns.net. = Community DNS </code></pre> It looks like a couple of the CommunityDNS nameservers are carrying a different version of the zone than the others:<p><pre><code> dkmpb:~ dknight$ dig -4 +nss io. SOA a0.nic.io. noc.afilias-nst.info. 1497256293 10800 3600 2764800 900 from server 65.22.162.17 in 38 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256292 10800 3600 2764800 900 from server 65.22.160.17 in 44 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256201 10800 3600 2764800 900 from server 194.0.2.1 in 62 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256293 10800 3600 2764800 900 from server 194.0.1.1 in 64 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256293 10800 3600 2764800 900 from server 65.22.161.17 in 98 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256293 10800 3600 2764800 900 from server 74.116.178.1 in 101 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256201 10800 3600 2764800 900 from server 74.116.179.1 in 107 ms. </code></pre> And a couple of them are giving bad response<p><pre><code> echo = Afilias dig +noall +norecur +cmd +answer +authority -4 +notcp @a0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @b0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @c0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS echo echo = Community DNS dig +noall +norecur +cmd +answer +authority -4 +notcp @ns-a1.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @ns-a2.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @ns-a3.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @ns-a4.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ====== Afilias ====== ; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @a0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256290 10800 3600 2764800 900 io. 86400 IN NS ns-a3.io. io. 86400 IN NS b0.nic.io. io. 86400 IN NS ns-a1.io. io. 86400 IN NS ns-a4.io. io. 86400 IN NS ns-a2.io. io. 86400 IN NS a0.nic.io. io. 86400 IN NS c0.nic.io. hostname.bind. 0 CH TXT &quot;ns087b.app22.iad1.afilias-nst.info&quot; hostname.bind. 0 CH NS hostname.bind. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net. shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns2.d-zone.ca. ; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @b0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256290 10800 3600 2764800 900 io. 86400 IN NS ns-a1.io. io. 86400 IN NS c0.nic.io. io. 86400 IN NS ns-a3.io. io. 86400 IN NS a0.nic.io. io. 86400 IN NS ns-a2.io. io. 86400 IN NS ns-a4.io. io. 86400 IN NS b0.nic.io. hostname.bind. 0 CH TXT &quot;ns087b.app12.lax1.afilias-nst.info&quot; hostname.bind. 0 CH NS hostname.bind. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns4.p23.dynect.net. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. ; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @c0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256290 10800 3600 2764800 900 io. 86400 IN NS ns-a1.io. io. 86400 IN NS c0.nic.io. io. 86400 IN NS ns-a4.io. io. 86400 IN NS ns-a2.io. io. 86400 IN NS ns-a3.io. io. 86400 IN NS b0.nic.io. io. 86400 IN NS a0.nic.io. hostname.bind. 0 CH TXT &quot;ns087b.app25.iad1.afilias-nst.info&quot; hostname.bind. 0 CH NS hostname.bind. shl.io. 86400 IN NS ns4.p23.dynect.net. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. ====== Community DNS ====== ; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @ns-a1.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256290 10800 3600 2764800 900 hostname.bind. 0 CH TXT &quot;NORM 002590-E2B186&quot; shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net. ; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @ns-a2.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256201 10800 3600 2764800 900 hostname.bind. 0 CH TXT &quot;COMM 002590-E2B186&quot; io. 900 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256201 10800 3600 2764800 900 ; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @ns-a3.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256290 10800 3600 2764800 900 hostname.bind. 0 CH TXT &quot;NORM 001B24-2DB609&quot; shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net. ; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @ns-a4.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256201 10800 3600 2764800 900 hostname.bind. 0 CH TXT &quot;COMM 001B24-2DB609&quot; io. 900 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256201 10800 3600 2764800 900</code></pre>

I tried loading redis.io and got the network error. I thought it was just their site but looks like a bigger issue with .io.

This affected my service as well. Where does the root of the problem lie, with the .IO service itself or somewhere else?

Yup, we&#x27;re also seeing this fail for Elastic Cloud (our ES provider which resolves to nodes on aws.found.io).

It affects also our website.<p>Is there any example of other TLDs having similar issues in past?

Not the first time .io has had issues: <a href="https:&#x2F;&#x2F;www.theregister.co.uk&#x2F;2017&#x2F;07&#x2F;10&#x2F;io_hijacking_in_transition_cockup&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.theregister.co.uk&#x2F;2017&#x2F;07&#x2F;10&#x2F;io_hijacking_in_tra...</a>

We were affected as well, but are back on ns-a[24].io. since about 1550Z.

You know, it&#x27;s ironic, but <a href="https:&#x2F;&#x2F;dnsspy.io" rel="nofollow">https:&#x2F;&#x2F;dnsspy.io</a> - which also uses the .io TLD - would alert whenever something like this happens, so you don&#x27;t have to spend hours debugging a DNS issue.

Ours (kasko.io) seems to be working again on both ns-a2 and ns-a4

Incomplete copy pasta, or your dig commands are off?

Yup, seeing this as well for one of our .io domains.

Also seeing this affect several of our .io domains.

Same here. Started 14:20 UK time (13:20 UTC).

.io had a similar issue beginning this year.

same issue here

We&#x27;re getting this as well.

it&#x27;s interesting, last night I was trying to get to sci-hub.io and all that showed up was a blank page. I assumed due to the nature of the site that maybe it was taken down but instead it&#x27;s a .io problem

Seems to be fixed now

Seeing the same issue

Having same issues

IO apears to have nameservers operated by Afilias, CommunityDNS, OneWorld DNS<p>$ for ns in $(dig +short io. IN NS | sort); do ip=$(dig +short ${ns} IN A); rev=$(host ${ip} | awk -Fpointer &#x27;{print $2}&#x27;); echo -n &quot;= $ns = $ip = $rev = &quot;; whois -h whois.ripe.net ${ip} | awk -F: &#x27;&#x2F;^descr:&#x2F; &amp;&amp; !&#x2F;RIPE&#x2F; {print $2}&#x27;; done<p>= a0.nic.io. = 65.22.160.17 = a0.nic.payu. = Afilias NS087 A0 = b0.nic.io. = 65.22.161.17 = b0.nic.payu. = Afilias NS087 B0 = c0.nic.io. = 65.22.162.17 = c0.nic.payu. = Afilias NS087 C0 = ns-a1.io. = 194.0.1.1 = ns1.communitydns.net. = ICB plc Anycast (via NetConnex AS21396), ICB plc Anycast (via Community DNS AS42909) = ns-a2.io. = 194.0.2.1 = ns-a2.io. = ICB plc Anycast (via Community DNS AS42909) = ns-a3.io. = 74.116.178.1 = b3-1.oneworlddns.net. = Community DNS = ns-a4.io. = 74.116.179.1 = b4-1.oneworlddns.net. = Community DNS<p>It looks like a couple of the CommunityDNS nameservers are carrying a different version of the zone than the others:<p>dkmpb:~ dknight$ dig -4 +nss io. SOA a0.nic.io. noc.afilias-nst.info. 1497256293 10800 3600 2764800 900 from server 65.22.162.17 in 38 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256292 10800 3600 2764800 900 from server 65.22.160.17 in 44 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256201 10800 3600 2764800 900 from server 194.0.2.1 in 62 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256293 10800 3600 2764800 900 from server 194.0.1.1 in 64 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256293 10800 3600 2764800 900 from server 65.22.161.17 in 98 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256293 10800 3600 2764800 900 from server 74.116.178.1 in 101 ms. SOA a0.nic.io. noc.afilias-nst.info. 1497256201 10800 3600 2764800 900 from server 74.116.179.1 in 107 ms.<p>And they&#x27;re giving bad responses<p>echo = Afilias dig +noall +norecur +cmd +answer +authority -4 +notcp @a0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @b0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @c0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS echo<p>echo = Community DNS dig +noall +norecur +cmd +answer +authority -4 +notcp @ns-a1.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @ns-a2.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @ns-a3.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS dig +noall +norecur +cmd +answer +authority -4 +notcp @ns-a4.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS echo<p>= Afilias<p>; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @a0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256301 10800 3600 2764800 900 io. 86400 IN NS c0.nic.io. io. 86400 IN NS ns-a4.io. io. 86400 IN NS b0.nic.io. io. 86400 IN NS a0.nic.io. io. 86400 IN NS ns-a3.io. io. 86400 IN NS ns-a1.io. io. 86400 IN NS ns-a2.io. hostname.bind. 0 CH TXT &quot;ns087b.app16.iad1.afilias-nst.info&quot; hostname.bind. 0 CH NS hostname.bind. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net.<p>; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @b0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256301 10800 3600 2764800 900 io. 86400 IN NS a0.nic.io. io. 86400 IN NS b0.nic.io. io. 86400 IN NS c0.nic.io. io. 86400 IN NS ns-a1.io. io. 86400 IN NS ns-a2.io. io. 86400 IN NS ns-a3.io. io. 86400 IN NS ns-a4.io. hostname.bind. 0 CH TXT &quot;ns087b.app10.lax1.afilias-nst.info&quot; hostname.bind. 0 CH NS hostname.bind. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net. shl.io. 86400 IN NS ns1.d-zone.ca.<p>; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @c0.nic.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256301 10800 3600 2764800 900 io. 86400 IN NS ns-a2.io. io. 86400 IN NS c0.nic.io. io. 86400 IN NS ns-a1.io. io. 86400 IN NS a0.nic.io. io. 86400 IN NS ns-a3.io. io. 86400 IN NS ns-a4.io. io. 86400 IN NS b0.nic.io. hostname.bind. 0 CH TXT &quot;ns087b.app9.iad1.afilias-nst.info&quot; hostname.bind. 0 CH NS hostname.bind. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns1.d-zone.ca.<p>= Community DNS<p>; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @ns-a1.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256301 10800 3600 2764800 900 hostname.bind. 0 CH TXT &quot;NORM 002590-E2B186&quot; shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net.<p>; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @ns-a2.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256301 10800 3600 2764800 900 hostname.bind. 0 CH TXT &quot;COMM 002590-E2B186&quot; shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net. = OneWorldDNS &#x2F; CommunityDNS?<p>; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @ns-a3.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256301 10800 3600 2764800 900 hostname.bind. 0 CH TXT &quot;NORM 001B24-2DB609&quot; shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net.<p>; &lt;&lt;&gt;&gt; DiG 9.8.3-P1 &lt;&lt;&gt;&gt; +noall +norecur +cmd +answer +authority -4 +notcp @ns-a4.io. io. IN SOA hostname.bind. CH TXT shl.io. IN NS ; (1 server found) ;; global options: +cmd io. 86400 IN SOA a0.nic.io. noc.afilias-nst.info. 1497256301 10800 3600 2764800 900 hostname.bind. 0 CH TXT &quot;COMM 001B24-2DB609&quot; shl.io. 86400 IN NS ns1.d-zone.ca. shl.io. 86400 IN NS ns2.d-zone.ca. shl.io. 86400 IN NS ns1.p23.dynect.net. shl.io. 86400 IN NS ns2.p23.dynect.net. shl.io. 86400 IN NS ns3.p23.dynect.net. shl.io. 86400 IN NS ns4.p23.dynect.net.

same

Same issue here! Luckily, all our API clients include a fallback domain.

Might be limited to Route 53: <a href="https:&#x2F;&#x2F;status.aws.amazon.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;status.aws.amazon.com&#x2F;</a>