|
|
|
|
|
|
by KennyBlanken
709 days ago
|
|
|
For anyone not well versed in DNS who needs an ELI5 level: This impacts anyone using HE.net for their domain name service because a domain name specifies its nameservers (in an NS record) using fully qualified domain names. I believe it's ns1.he.net and ns2.he.net. User at WildISP tries to go to a site. Resolving nameserver at WildISP.net fetches the NS records for samplewhamplesite.com from a root server and gets pointed to ns1.he.net...which no longer exists because the entire domain disappeared from the root servers. It looks like things are back up? Edit: nope, still in clienthold. |
|
|