Nslookup and dig

Barry Margolin barmar at alum.mit.edu
Thu Apr 24 02:24:46 UTC 2008


In article <fumqpa$jcb$1 at sf1.isc.org>,
 "Bob Hoffman" <bob at bobhoffman.com> wrote:

> I have been playing around with different setups and finding bind quite
> interesting.
> 
> I have come across a peculiar item..
> 
> I added a website and am able to resolve it via ftp, http, and mail, no
> problem...very quick and no errors.
> 
> I can use dig on my site and any other site and it works fine.
> However, if I do nslookup on my site it 'can't find it'. Yet if I do dig on
> my site, it works fine.
> 
> From my terminal via putty, using my server to look:
> 
> typing dig mysite.com gets a good answer
> Typing dig google.com gets a good answer
> Typing nslookup google.com get a good answer
> Typing nslookup mysite.com gets error 'cant' find.
> 
> Yet, I can ftp, mail, http, and everything else no problem. In fact
> everything seems fine.
> 
> Seems like a quaint issue.... Anyone else ever have this issue?

Well, nslookup is a lousy tool.

What's the REAL domain this is happening with?  Does it only happen when 
you use nslookup on your computers, or does it happen when you use 
nslookup in other locations as well?

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***


More information about the bind-users mailing list