->If I'm running www.somedomain.com, and my nameserver
->is a.ns.somedomain.com, how will other hosts be able
->to resolve that name? Or am I just confused about the
->DNS lookup process, and hosts don't use the
->nameserver's name at all? I'm just a little worried
->because I'm supposed to be transferring a client's
->domain to my machine tomorrow.
Yeah it's kinda odd..
Let's assume we're dealing with somedomain.net .
When you first register somedomain.net the registrar asks you for the DNS
info and you provide:
ns1.somedomain.net
1.2.3.4
ns2.somedomain.net
1.2.3.5
Then you setup the ns records in tinydns's root directory and make the
cdb. Make sure to add-ns for both 1.2.3.4 and 1.2.3.5 as well don't
forget add aliases (add-alias) for ns1.somedomain.net and
ns2.somedomain.net.
As far as the registrar is concerned somedomain.net's DNS is provided by
ns1.somedomain.net. But wait what is ns1.somedomain.net? That's what you
provided the IP's for in the first place. It's kinda recursive and wonky
but it makes sense in perspective.
A registrar just serves up the MAIN NS info for domains. It it up to the
domains to provide their dns (or delgate to another dns provider like
granitecanyon.com or something). When you register a domain you tell the
registrar who takes care of that domain not the machine that's supposed to
be pointed to by that domain name.
Hopefully that was helpful...
--
Sean Cody (seanc@pangea.ca)
"Teach a man to make fire, and he will be warm for a day.
Set a man on fire, and he will be warm for the rest of his life."
- John A Hrastar
|