3 ms·
The attack is on the authoritative name servers, not a DNS resolver. A public DNS resolver will query the authoritative name server for a record if it doesn't e
by sinap 10y ago
The attack is on the authoritative name servers, not a DNS resolver. A public DNS resolver will query the authoritative name server for a record if it doesn't exist in it's cache.
- mgamble 10y agoAgreed, but there is nothing stopping you from having the authoritative name servers for a domain with different providers. As someone previously said, DNS was designed for this.
- Symbiote 10y agoIt's used to be common for universities to do this, mine still does: ic.ac.uk. 45665 IN NS ns1.ic.ac.uk. ic.ac.uk. 45665 IN NS ns2.ic.ac.uk. ic.ac.uk. 45665 IN NS ns0.ic.ac.uk. ic.ac.uk. 45665 IN NS authdns1.csx.cam.ac.uk. (and Cambridge use Imperial College as a secondary) but the best-known American universities are on cloud providers now.
- jrochkind1 10y agoCan you have secondary name servers too though? And would it have worked to avoid outage for domains doing such in this case?