arstechnica , 1 month ago DNS glitch that threatened Internet stability fixed; cause remains unclear For 4 days, the c-root server maintained by Cogent lost touch with its 12 peers. https://arstechnica.com/security/2024/05/dns-glitch-that-threatened-internet-stability-fixed-cause-remains-unclear/?utm_brand=arstechnica&utm_social-type=owned&utm_source=mastodon&utm_medium=social
DNS glitch that threatened Internet stability fixed; cause remains unclear
For 4 days, the c-root server maintained by Cogent lost touch with its 12 peers.
https://arstechnica.com/security/2024/05/dns-glitch-that-threatened-internet-stability-fixed-cause-remains-unclear/?utm_brand=arstechnica&utm_social-type=owned&utm_source=mastodon&utm_medium=social
barryjsullivan , 1 month ago @arstechnica Did anyone try to turn it off and back on?
@arstechnica Did anyone try to turn it off and back on?
karlauerbach , 1 month ago @arstechnica The a-, b--, c-, etc root servers do not really talk to one another. Rather they fetch their master zone file from Verisign who has a contract to maintain the root zone file. The DNSSEC anchor file is obtained from IANA. How a root server operator deploys these files through their anycast suite of actual physical servers is pretty up to the root server operator.
@arstechnica The a-, b--, c-, etc root servers do not really talk to one another.
Rather they fetch their master zone file from Verisign who has a contract to maintain the root zone file.
The DNSSEC anchor file is obtained from IANA.
How a root server operator deploys these files through their anycast suite of actual physical servers is pretty up to the root server operator.