The following command will get the name server IP address from a root server: $ dig @a.gtld-servers.net ns1.mystyka.com
You'll see that it gives the IP address of ns1.mystyka.com even though ns1.mystaka.com isn't answering right now. You'll find that all root servers know the NS records of every domain they are authoritative for. This is accomplished by your registrar when you register a domain -- you have to enter the NS records and the registrar then passes the updates to the root servers. The root servers aren't going to respond to queries for A records, but they will answer iterative requests for authoritative name servers of a particular domain. My favorite way to see the hierarchy is: $ dig . $ dig int. $ dig un.int. $ dig org. $ dig apache.org. $ dig com. $ dig redhat.com. $ dig us. $ dig it. etc. (credit to the O'Reily DNS & BIND book for pointing out the command above). mjb On Sun, 2003-03-30 at 21:08, Larry Brown wrote: > If I simply run a dig mystyka.com ns I get a failed attempt as the name > server is not responding. If I run your query with +trace it shows the > nameservers by name. If the domain cannot be contacted to resolve the names > of the name servers to there must be some way that the root must tell the > dns query what address the name servers are at. How can you get the name > server IP addresses from the root servers? +trace just times out looking > for any record except ns and for ns it doesn't show what it has for IP > addresses for them. > > Larry S. Brown > Dimension Networks, Inc. > (727) 723-8388 > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Cowles, Steve > Sent: Sunday, March 30, 2003 10:37 PM > To: '[EMAIL PROTECTED]' > Subject: RE: NameServer, DNS, and BIND > > > -----Original Message----- > > From: Larry Brown > > Sent: Sunday, March 30, 2003 6:42 PM > > Subject: RE: NameServer, DNS, and BIND > > > > > > My apologies for a feeble attempt at finding the problem. If > > whois has yet to be updated and the change has in fact been > > made at the root servers as reflected by that dig request, how > > do you find out the ip address associated with those name > > servers that came back from the dig request to make sure his > > server is even getting the requests? I'm not versed on dig > > and don't know how to shovel up that information. > > > > To find the ip address (a record) associated with a fqdn... > > dig ns1.mydomain.com a > > To find the name server record (ns) for a domain... > > dig mydomain.com ns > > Issue a query to ns1.mydomain.com for the domain name mydomain.com and > return the ns record > > dig @ns1.mydomain.com mydomain.com ns > > Basically just specify the "type" of dns record to return at the end of dig. > Some of the well known record types are: ns, a, soa, mx, cname > > Also, to find the reverse lookup record (PTR) for ip 1.2.3.4 > > dig -x 1.2.3.4 > > Steve Cowles > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list -- Mark Johnson-Barbier
signature.asc
Description: This is a digitally signed message part
