This is a discussion on Re: Why would win2k's nslookup trigger a call to root servers and host, dig not? within the Bind Users forums, part of the DNS and Related Forums category; In article <bvegsl$qrb$1@sf1.isc.org>, eel@javabox.com (Eel) wrote: > Hi, > I've ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
In article <bvegsl$qrb$1@sf1.isc.org>, eel@javabox.com (Eel) wrote:
> Hi, > I've intalled some new name servers and I've found that when > running nslookup on win2k to a new server it triggers a call to root > dns servers even though the particular domains are included in that > server's zones. If I look up the names with either Linux host or dig > on that server, the root doesn't get called. > > Is there any difference on the type of queries that these tools use? > I really don't want to open up calls to the root servers because it > seems like a waste of bandwidth when it's not needed. Turn on query logging, or enable verbose mode in nslookup, to see precisely what queries are being performed. Anyway, why do you care what nslookup does? You should concern yourself with supporting ordinary applications. Quirks of debugging utilities are not usually a serious issue. -- Barry Margolin, barmar@alum.mit.edu Arlington, MA |
![]() |
| Thread Tools | |
| Display Modes | |
|
|