|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Stay one step ahead of the competition. Evaluate and give feedback
on some of the hottest web development tools on the market today.
Make your opinion heard! Click
Here
|
|
#1
|
|||
|
|||
|
Domain name with nameservers on another domain
Ok, I'm still having trouble grasping the entire concept of how DNS works and was hoping one of you guys can help me out.
From a book I've been reading, I understand that registrars are responsible for providing the registry operator for the gTLD which consists of the second level domain name and the name and ip addresses of the authoritative dns servers for the domain. However, I don't understand how it works if you don't want to register nameservers for that domain and you want to use nameservers on another domain. Example: I have a domain section31.us Using dave's tool I make a query for that domain and I get this. Code:
Querying a.root-servers.net (198.41.0.4)... delegated
Querying I.GTLD.BIZ (156.154.96.126)... delegated
Querying NS2.DREAMHOST.COM (208.96.10.221)...
Received authoritative response
My question is, since that nameserver is hosted on another domain, how does it know the ip of NS2.DREAMHOST.COM without performing a whole new dns query for dreamhost.com? -- Last edited by section31 : April 9th, 2008 at 09:29 AM. |
|
#2
|
||||
|
||||
|
Funny guy, so you'd rather tell me about this post in IRC rather than simply get your answers there or via email. Alrighty, then.
Ok, so here's your query for section31.us again: resolve section31.us I think you're asking how it knows that "ns3.dreamhost.com" (for example) resolves to 66.33.216.216 without doing an extra lookup. It doesn't - unless the dns server has previously made this request and cached the answer. Also, click the aqua colored "C.GTLD.BIZ" to see its response. resolve section31.us via C.GTLD.BIZ Notice that it only lists the 3 name servers without any IPs. But now let's click on "ns1.dreamhost.com" and then roll back to "G.GTLD-SERVERS.NET" by clicking on it. resolve ns1.dreamhost.com via G.GTLD-SERVERS.NET Now you see that the IP addresses are provided along with the name server domains. This means an extra lookup does not have to take place - ever.
__________________
Send me a private message if you would like me to setup your DNS for you for a price of your choosing. This is the preferred method if your DNS needs to be fixed/setup fast and you don't have the time to bounce messages back and forth on a forum. Also, check out these links: Whois Direct | DNS Crawler | NS Trace | Compare Free DNS Hosts |
|
#3
|
|||
|
|||
|
Thanks for the reply, but I'm still confused lol.
The tld nameserver that holds the records for section31.us is C.GTLD.BIZ and not G.GTLD-SERVERS.NET. So the fact that you are saying G.GTLD-SERVERS.NET has the ips to ns1.dreamhost.com...doesn't that make it a an extra lookup? |
|
#4
|
||||
|
||||
|
"I think you're asking how it knows that "ns3.dreamhost.com" (for example) resolves to 66.33.216.216 without doing an extra lookup. It doesn't - unless the dns server has previously made this request and cached the answer."
By saying "It doesn't" I was disagreeing with the point that it can go "without doing an extra lookup". Cancel out the double negatives, and you'll see that the post is basically saying: "Yes, it has to do an extra lookup and here's the proof, but it isn't a big deal cause of dns caching". |
|
#5
|
|||
|
|||
|
Ah I see, thanks for the reply dave. You're the best.
|
![]() |
| Viewing: Dev Shed Forums > System Administration > DNS > Domain name with nameservers on another domain |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|
|