DNS Maintenance issues

After extensive research and testing, we learned that our DNS provider performed maintenance this morning too, at the same time as our internal maintenance. During this maintenance they shut-off a DNS server that had been decommissioned 4 weeks ago. In preparation of this, we had changed our DNS settings 4 weeks ago to indicate that this old server should not longer be used.

Unfortunately, it seems that certain servers from these ISP's are not respecting the 1 day validity (TTL / Time-to-live) on these DNS records, and were still contacting this old server, even though we indicated not to use those servers anymore 4 weeks ago.

We worked with our DNS provider and the decommissioned server has been restored for now. We are working on contacting the ISP's that are not following the internet standards for DNS TTL, in order to prevent this issue from returning at a later date.

We have been working hard to increase the capacity of our DNS infrastructure. However, due to a rise in reported errors, we rolled back the changes at 10:38 AM.

The rollback has resolved the issue, but since some internet providers enforce DNS caching with a max TTL of 24 hours, the solution may not yet be applied for all users.

To bypass the ISP TTL cache you can temporarily change the DNS server on your computer to Cloudflare (1.1.1.1 / 1.0.0.1) or Google (8.8.8.8 / 8.8.4.4).