DNS resolution interrupted for some domains

Update timeline

1. investigating Oct 26, 2026, 01:00 AM UTC

   Some domains stopped resolving.

2. investigating Oct 26, 2026, 06:00 AM UTC

   We have received reports of domains no longer resolving. Our team is investigating.

3. identified Oct 26, 2026, 09:00 AM UTC

   Our primary nameserver [ns1.yorkdns.com](http://ns1.yorkdns.com) is experiencing a storage failure. Our secondary nameserver [ns2.yorkdns.com](http://ns2.yorkdns.com) is handling requests, but some domains are still affected. Work is in progress on ns1.

4. monitoring Oct 26, 2026, 09:25 AM UTC

   [ns1.yorkdns.com](http://ns1.yorkdns.com) has been repaired and is back in service. DNS resolution is restored for all domains. We are continuing to check replication between our two servers.

5. monitoring Oct 26, 2026, 09:55 AM UTC

   We identified a replication issue: some zones were not being transferred to [ns2.yorkdns.com](http://ns2.yorkdns.com). These zones have been fixed and are now served by both servers.

6. monitoring Oct 26, 2026, 10:25 AM UTC

   All zones are now identical on ns1 and ns2\. DNS redundancy is fully operational. We are continuing to monitor.

7. resolved Oct 26, 2026, 10:45 AM UTC

   This incident has been resolved. All domains are served by both of our nameservers, and enhanced monitoring has been put in place. A detailed report will be published shortly.

8. investigating Oct 26, 2026, 11:15 AM UTC

   $34