The below is purely anecdotal. I saw something similar yesterday for about the same duration. This was around 18:15 PDT (UTC-7).
I saw what I can only describe as "slow responses" from authoritative NSes for root-servers.net (responsible for .) and gtld-servers.net (responsible for .com). What I couldn't determine was whether or not this was network-level (i.e. IP backbone issues) or with the actual NS themselves: by the time I had set up tools and relevant bits to delve deeper into both possibilities simultaneously, it had disappeared. I don't use my ISPs nameservers, Google, Verizon, or OpenDNS -- I run my own caching NS that utilises named.cache/named.root -- so this wasn't a case of "maybe your upstream ISPs DNS was slow". -- | Jeremy Chadwick [email protected] | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | On Fri, Mar 24, 2017 at 05:52:08PM -0400, Charles D'Aoust via Outages wrote: > We've seen spikes in resolution times during the afternoon on all of our > recursive DNS (everywhere in the country) for about 10 minutes this > afternoon. The issue resolved itself before I could see anything wrong. > > Can anybody confirm seeing such an outage/slowness? This event occurred > between 15:00 and 15:30 EDT. > --- > Charles D’Aoust > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
