The brunt of the question is this -- What is the relationship between the primary nameserver specified in the
SOA record and the nameservers specified in the
NS records. How are these things linked?
When I query most websites, I get this:
dhamma@sansa:~$ host -t SOA arth.com arth.com has SOA record ns1.comcastbusiness.net. domreg-tech.comcastbusiness.net. 2009072715 3600 7200 604800 7200
And I expect to see
ns1.comcastbusiness.net as the primary nameserver, because when I query the
NS record for the domain I get this:
dhamma@sansa:~$ host -t NS arth.com arth.com name server ns1.comcastbusiness.net. arth.com name server ns2.comcastbusiness.net. arth.com name server ns3.comcastbusiness.net.
This always led to me thinking that the
SOA records somehow auto-populated the primary
NS record? Is that even remotely true?
Because here's where I'm most confused:
dhamma@sansa:~$ host -t SOA paulwarnk.com paulwarnk.com has SOA record a.dns.hostway.net. hostmaster.siteprotect.com. 2009012319 86400 7200 86400 99999
But I'm told, and do, use these nameservers:
dhamma@sansa:~$ host -t NS paulwarnk.com paulwarnk.com name server adns.cs.siteprotect.com. paulwarnk.com name server bdns.cs.siteprotect.com.
Why is this nameserver
adns.cs.siteprotect.com not listed as the primary nameserver in the