8.2.3-T4B core dumps under Solaris 2.6
Dave DeChellis
ddechell at lynx.dac.neu.edu
Thu Apr 27 14:47:28 UTC 2000
Hello,
The latest release of BIND (8.2.3-T4B) seems to be core dumping often.
Previous to T4B we were running T1A
with no problems.
So far we have identified two reasons:
1. Lookup for that makes use of global forwarders (i.e. Forward by
zone works).
2. Using NSLOOKUP, set type=soa, then lookup an A record causes core
dump for any zone (including zone
we are authoritative for).
3. Other yet unresolved...
named -v:
named 8.2.3-T4B Thu Apr 27 08:28:14 EDT 2000
root at venus:/tmp/823/src/bin/named
from named -d1 (lookup of www.hp.com)
datagram from [10.10.10.10].1076, fd 22, len 28
req: nlookup(www.hp.com) id 12 type=1 class=1
req: found 'www.hp.com' as 'com' (cname=0)
req: found 'www.hp.com' as 'com' (cname=0)
then named dies. -d9 produces (lookup of cnnfn.com):
datagram from [192.223.225.184].1040, fd 22, len 27
ns_req(from [192.223.225.184].1040)
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; cnnfn.com, type = A, class = IN
req: nlookup(cnnfn.com) id 9 type=1 class=1
req: found 'cnnfn.com' as 'com' (cname=0)
req: found 'cnnfn.com' as 'com' (cname=0)
findns: np 0xd20b4 'com'
findns: np 0xce91b8 ''
findns: 13 NS's added for ''
ns_forw()
qnew(0xec1cb0)
find_zone(cnnfn.com, 1)
find_zone: unknown zone
find_zone(com, 1)
find_zone: unknown zone
find_zone(., 1)
find_zone: existing zone 476
nslookup(nsp=0xefffe490, qp=0xec1cb0, "cnnfn.com")
nslookup: NS "G.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 2 ns addrs
nslookup: NS "F.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 3 ns addrs
nslookup: NS "B.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 4 ns addrs
nslookup: NS "J.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 5 ns addrs
nslookup: NS "K.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 6 ns addrs
nslookup: NS "L.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 7 ns addrs
nslookup: NS "M.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 8 ns addrs
nslookup: NS "I.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 9 ns addrs
nslookup: NS "E.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 10 ns addrs
nslookup: NS "D.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 11 ns addrs
nslookup: NS "A.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 12 ns addrs
nslookup: NS "H.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 13 ns addrs
nslookup: NS "C.ROOT-SERVERS.NET" c=1 t=2 (flags 0x2)
nslookup: 14 ns addrs
nslookup: 14 ns addrs total
then named dies.
Any thought or insight?
Thanks
Dave
More information about the bind-users
mailing list