Why would win2k's nslookup trigger a call to root servers and host, dig not?

This is a discussion on 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; Hi, I've intalled some new name servers and I've found that when running nslookup on win2k to a ...


Go Back   Usenet Forums > DNS and Related Forums > Bind Users

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 01-30-2004
Eel
 
Posts: n/a
Default Why would win2k's nslookup trigger a call to root servers and host, dig not?

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.

Is it safe to assume that nslookup on win2k is just quirky or will
other lookups be timing out?


Thanks.

Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 08:33 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0