nslookup problems

[Barry Margolin]

In article <384E67BE.9FA73271 at ziplink.net>,
News Administrator  <news at ziplink.net> wrote:
>Sorry.  Maybe I should clarify that the domains in question are outside of our
>network.  They are not our domains.  If I go to other nameservers, they see
>these domains just fine, but our nameservers don't.  Why is that?  This is
>only since the upgrade to 8.2.2p5

More curious is that when I go to your nameserver and try the same query,
it works fine.  The only difference is that I'm using dig, not nslookup.
If you insist on using nslookup, I suggest you turn on the debug option so
you can see precisely what queries it's sending; as the other poster said,
nslookup sometimes tries to do more than you tell it to.

tools:~#1013% dig sibor.com a @picnic.ziplink.net

; <<>> DiG 2.2 <<>> sibor.com a @picnic.ziplink.net 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr aa rd ra; Ques: 1, Ans: 1, Auth: 2, Addit: 2
;; QUESTIONS:
;;	sibor.com, type = A, class = IN

;; ANSWERS:
sibor.com.	86400	A	207.221.47.232

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.