Note: Someone linked to Why does DNS work the way it does? as a possible duplicate. But this link does not answer my question. Specifically, this link does not describe where exactly a regular domain name buyer like me (who has no DNS administration experience) sets the authoritative nameserver. All an inexperienced domain buyer like me does is set edit the DNS field for my domain in a reseller website like Godaddy or Namecheap and set it to customer nameservers like ns1.digitalocean.com
, ns2.digitalocean.com
, etc. The visible output I see after doing this is these nameservers appearing in the whois <mydomain>
output. Is this equivalent to setting the authoritative nameserver as well, or is there something more to it?
Say I register a domain named example.com
using any popular domain name registration service/reseller.
Say I have two Linux VMs hosted on two different cloud service provider's infrastructure.
Say I create DNS entries for example.com
using the DNS Manager of both cloud service providers. On the first cloud, I point example.com
to the IP address of the VM on the first cloud. On the second cloud, I point example.com
to the IP address of the VM on the second cloud.
When an Internet user performs nslookup
or dig
on example.com
which IP address would example.com
resolve to for it?
As per HBruijn's comment below, it would resolve to the IP address in the record of the authoritative nameserver. So my question is where in this whole process of registering a domain name by an inexperienced user like me on a popular domain name reseller service do we specify the authoritative nameserver?
Is it the DNS field that resellers like Godaddy or Namecheap ask us to enter? I thought that DNS field only appears in the whois
output. Does the reseller go and update the DNS too with the same nameservers as the authoritative nameservers?