4 ms·
Response from AWS Support: We have investigated this issue and are seeing incorrect responses from two of the .io nameservers: ns-a4.io and ns-a2.io. These na
by bscanlan 10y ago
Response from AWS Support:
We have investigated this issue and are 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).
- tbarbugli 10y agonice that they replied to you. Still waiting to see a reply from them...
- bscanlan 10y agoEnterprise Support customer here :) It looks like the bad .io servers aren't responding to requests anymore, at least from my location. I have flushed a bunch of my own records on public Google DNS: https://developers.google.com/speed/public-dns/cache https://developers.google.com/speed/public-dns/cache
- JelteF 10y agoThose broken .io nameservers seem to be taken down now. So next cache flush should fix the issue.