problem with one set of nameservers (diginsite.com)

[John Marble]

Now the problem is with multiple domains.  Are there compatibility isuues
with BIND 8.2.1 and BIND 4.9.4 (which is the version we are running)?


John Marble wrote:

> Our name server cannot resolve addresses for dcu.org using nslookup.
> $nslookup www.dcu.org
> ***can't find www.dcu.org: Non-existent host/domain
>
> The nameservers for dcu.org are
> ns1.diginsite.com       internet address = 208.2.188.5
> ns2.diginsite.com       internet address = 208.2.189.5
>
> If I tell nslookup the nameserver to use explicitly it resolves the
> addresses just fine.
> $nslookup www.dcu.org ns1.diginsite.com
> Server:  NS1.diginsite.com
> Address:  208.2.188.5
>
> Name:    www.dcu.org
> Address:  208.2.188.45
>
> However, when I let our nameserver determine the diginsite.com servers
> the query fails.  With debugging turned on I see our name server talk to
> the root servers and learn the correct name servers,
> followed by queries to them.
> req: nlookup(www.dcu.org) id 45006 type=1 class=1
> req: found 'www.dcu.org' as 'org' (cname=0)
> forw: forw -> [128.8.10.90].53 ds=23 nsid=59886 id=45006 45ms retry 4sec
>
> datagram from [128.8.10.90].53, fd 22, len 117; now Mon Oct 11 11:44:49
> 1999
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59886
> ;; flags: qr; Ques: 1, Ans: 0, Auth: 2, Addit: 2
> ;; QUESTIONS:
> ;;      www.dcu.org, type = A, class = IN
>
> ;; AUTHORITY RECORDS:
> DCU.org.        172800  IN      NS      NS1.DIGINSITE.COM.
> DCU.org.        172800  IN      NS      NS2.DIGINSITE.COM.
>
> ;; ADDITIONAL RECORDS:
> NS1.DIGINSITE.COM.      172800  IN      A       208.2.188.5
> NS2.DIGINSITE.COM.      172800  IN      A       208.2.189.5
>
> rrsetupdate: DCU.org
> rrsetcmp: name not in database
> rrsetupdate: DCU.org 0
> rrsetupdate: DCU.org 0
> resp: nlookup(www.dcu.org) qtype=1
> resp: found 'www.dcu.org' as 'dcu.org' (cname=0)
> sysquery: send -> [128.8.10.90].53 dfd=23 nsid=59101 id=0
> retry=939656693
> sysquery: send -> [128.8.10.90].53 dfd=23 nsid=56315 id=0
> retry=939656693
>
> datagram from [128.8.10.90].53, fd 22, len 128; now Mon Oct 11 11:44:49
> 1999
> rrsetupdate: NS1.DIGINSITE.COM
> rrsetcmp: no records in database
> rrsetupdate: NS1.DIGINSITE.COM 0
> rrsetupdate: DIGINSITE.com
> rrsetcmp: no records in database
> rrsetupdate: DIGINSITE.com 0
> rrsetupdate: DIGINSITE.com 0rrsetupdate: NS1.DIGINSITE.COM
> rrsetcmp: rrsets matched
> rrsetupdate: NS2.DIGINSITE.com
> rrsetcmp: no records in database
> rrsetupdate: NS2.DIGINSITE.com 0
>
> datagram from [128.8.10.90].53, fd 22, len 128; now Mon Oct 11 11:44:49
> 1999
> rrsetupdate: NS2.DIGINSITE.COM
> rrsetcmp: rrsets matched
> rrsetupdate: DIGINSITE.com
> rrsetcmp: rrsets matched
> rrsetupdate: NS1.DIGINSITE.com
> rrsetcmp: rrsets matched
> rrsetupdate: NS2.DIGINSITE.COM
> rrsetcmp: rrsets matched
>
> datagram from [xxx.xxx.xxx.xxx].37029, fd 22, len 29; now Mon Oct 11
> 11:44:54 199
> 9
> req: nlookup(www.dcu.org) id 45006 type=1 class=1
> req: found 'www.dcu.org' as 'dcu.org' (cname=0)
> forw: forw -> [208.2.188.5].53 ds=23 nsid=41618 id=45006 0ms retry 4sec
> resend(addr=1 n=0) -> [208.2.189.5].53 ds=23 nsid=41618 id=45006 0ms
> resend(addr=0 n=1) -> [208.2.188.5].53 ds=23 nsid=41618 id=45006 0ms
>
> datagram from [xxx.xxx.xxx.xxx].37029, fd 22, len 29; now Mon Oct 11
> 11:45:04 199
> 9
> req: nlookup(www.dcu.org) id 45006 type=1 class=1
> req: found 'www.dcu.org' as 'dcu.org' (cname=0)
> resend(addr=1 n=1) -> [208.2.189.5].53 ds=23 nsid=41618 id=45006 0ms
> resend(addr=0 n=2) -> [208.2.188.5].53 ds=23 nsid=41618 id=45006 0ms
>
> datagram from [xxx.xxx.xxx.xxx].37029, fd 22, len 29; now Mon Oct 11
> 11:45:24 199
> 9
> req: nlookup(www.dcu.org) id 45006 type=1 class=1
> req: found 'www.dcu.org' as 'dcu.org' (cname=0)
> resend(addr=1 n=2) -> [208.2.189.5].53 ds=23 nsid=41618 id=45006 0ms
> send_msg -> [xxx.xxx.xxx.xxx].37029 (UDP 22) id=45006
>
> But I never get any response back.   Anyone have any ideas?  Our
> ISP confirms they see the packets leave their network with the correct
> destinations but they see no response either.  Puzzling problem.  We are
> running BIND 4.94.  I have tested
> other systems on 4.94 not on our network and they work fine.  I can
> duplicate the problem within our network which leads
> me to believe it is an external routing problem.  But then, I do not
> understand why I can explicitly state the name server to use and get a
> result if it is a routing issue to ns1.diginsite.com.  Not sure what to
> try next.  I'd appreciate any help on this one.
>
> --
> John Marble
> jmarble at jhancock.com



--
John Marble
Unix Support Group
John Hancock Financial Services
jmarble at jhancock.com
617-572-7053