topic Re: BIND 9.3 problem in Operating System - HP-UX

BIND 9.3 problem

Pavol Halcin — Wed, 19 Mar 2008 12:45:20 GMT

Hello,

we have recently migrated our old DNS (11.11/BIND 8.1.2) to new systems with 11.23/BIND 9.3.2. After the migration, all systems have problems resolving non-existent domains, f.e.:

*** WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0167.qqq.nxst) took 20 seconds
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 20 seconds

From named query log:

19-Mar-2008 14:16:15.805 queries: info: client 10.32.52.93#40733: query: www.doesnotexist0167.qqq.nxst IN A +
19-Mar-2008 14:16:25.807 queries: info: client 10.32.52.93#40733: query: www.doesnotexist0167.qqq.nxst IN A +
19-Mar-2008 14:16:35.809 queries: info: client 10.32.52.93#40739: query: www.doesnotexist0167.qqq.nxst.xxxx.xx IN A +
19-Mar-2008 14:16:35.809 queries: info: client 10.32.52.93#40739: query: www.doesnotexist0167.qqq.nxst.xxxx.yyy IN A +
19-Mar-2008 14:16:35.810 queries: info: client 10.32.52.93#40739: query: www.doesnotexist0167.qqq.nxst.nt.xxxx.yyy IN A +
19-Mar-2008 14:16:35.811 queries: info: client 10.32.52.93#40739: query: www.doesnotexist0167.qqq.nxst.xxxxnet.yyy IN A +
19-Mar-2008 14:16:35.812 queries: info: client 10.32.52.93#40739: query: www.doesnotexist0167.qqq.nxst.xxxxroot.yyy IN A +
19-Mar-2008 14:16:35.812 queries: info: client 10.32.52.93#40739: query: www.doesnotexist0167.qqq.nxst.xxxxxx.yyyyyyyy.zz.com IN A +

The whole process takes 20 seconds. When I edit resolv.conf to use the old DNS servers, everything works fine.
Any idea where the problem might be?

Re: BIND 9.3 problem

Steven E. Protter — Wed, 19 Mar 2008 12:49:11 GMT

Shalom,

I suspect the problem is the data on the new DNS servers.

BIND comes with a utility called named-checkzone that lets you check and correct the contents of your various zone database record files.

SEP

Re: BIND 9.3 problem

Pavol Halcin — Wed, 19 Mar 2008 12:58:40 GMT

That has allready been checked, all zones are OK. The resolving of all systems in the nameserver configuration works fine, but when I try to resolve something that is not in our environment or does not exist, it takes 20 seconds to reply that the host does not exist.
With the old DNS, we receive the message immediately.

Re: BIND 9.3 problem

Pavol Halcin — Wed, 19 Mar 2008 14:13:24 GMT

Issue solved by disabling recursion in named.conf

Re: BIND 9.3 problem

Pavol Halcin — Wed, 19 Mar 2008 14:14:09 GMT