Problem w/ 8.2.1 ( was: possible problem w/ 8.2.1)

bas aerts bas_aerts at ins.com
Fri Jul 2 10:12:46 UTC 1999


I also have this problem with the 'lame' servers and stuff:


Jul  1 17:35:05 amsftp00 named[2572]: ns_forw: query(w16.hitbox.com) A RR
negati
ve cache entry (AUTH02.NS.UU.NET.com:)
Jul  1 17:37:47 amsftp00 named[2572]: Response from unexpected source
([194.178.
56.6].53)
Jul  1 17:38:07 amsftp00 named[2572]: Lame server on 'ugc.com' (in
'ugc.com'?):
[198.62.195.99].53 'PEGASUS.CVG-GRP.COM'
Jul  1 17:38:12 amsftp00 named[2572]: ns_forw: query(ugc.com) All possible A
RR'
s lame

What's going on here?

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Martin, Kevin
Sent: Thursday, July 01, 1999 5:41 PM
To: 'Bind Users Mailing List'
Subject: Problem w/ 8.2.1 ( was: possible problem w/ 8.2.1)


Let's try this again.  Barry was helping me but I don't know if he's given
up on me or is working on a solution.

Here's the relevant facts:

OS version HPUX 10.20
Bind version 8.2.1

/etc/resolv.conf has a "search" directive of "il.nb.com nb.com"

Looking up a host in "nc.nb.com"

nslookup of "host.nc" returns a "Server failed" message
nslookup of "host.nc.nb.com" returns the correct information.
nslookup -d2 of "host.nc" shows an attempt to find the host as
"host.nc.il.nb.com", but that's where it ends.
dig @dns1 host.nc.il.nb.com returns:


; <<>> DiG 8.2 <<>> @dns1 host.nc.il.nb.com
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 6
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;; host.nc.il.nb.com, type = A, class = IN

;; Total query time: 4 msec
;; FROM: dns1 to SERVER: dns1 10.216.34.4
;; WHEN: Tue Jun 29 11:12:07 1999
;; MSG SIZE sent: 42 rcvd: 42



After reinstalling Bind version 8.1.2, the same lookup results in:

nslookup of "host.nc" returns the correct information.
nslookup of "host.nc.nb.com" returns the correct information.
nslookup -d2 of "host.nc" shows an attempt to find the host as
"host.nc.il.nb.com", and then as "host.nc.nb.com" which then returns the
correct info.
dig @dns1 host.nc.il.nb.com returns:



; <<>> DiG 8.1 <<>> @dns1 host.nc.il.nb.com
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUERY SECTION:
;;      host.nc.il.nb.com, type = A, class = IN

;; AUTHORITY SECTION:
il.nb.com.           2H IN SOA       dns1.il.nb.com.
dnsmaster.dns1.il.nb.com. (
                                        1999070102      ; serial
                                        1H              ; refresh
                                        15M             ; retry
                                        1W              ; expiry
                                        2H )            ; minimum


;; Total query time: 15 msec
;; FROM: dns1 to SERVER: dns1  10.216.34.4
;; WHEN: Thu Jul  1 09:09:09 1999
;; MSG SIZE  sent: 42  rcvd: 105


Dig v 8.2 gives the same results as the above dig w/ v8.1 against the v
8.1.2 nameserver ( so it's not dig that's the problem ).
Has anybody had a chance to look at this or been able to duplicate it?



Kevin Martin
Bank of America - CRT
Firewall/DNS/SMTP/Network Admin.
kevinm at crt.com



More information about the bind-users mailing list