Intermittent Resolution problems

[Kevin Darcy]

Without any specifics, one can only guess. Sounds like you're getting bad
referral information from somewhere. Why don't dump your database (via "ndc
dumpdb" or an INT signal to the nameserver process) and see what your
nameserver knows about the problematic names? To have your nameserver track
more detail, at the expense of higher memory consumption, turn on
"host-statistics yes" in your options clause.


- Kevin
JO wrote:

> We run bind 8.2.2.-P5 on HP-UX 10.20.  Our server resolves other domains
>
>  MOST of the time.  At times queries for hosts in other domains returns
> 'no
>  such host or domain', yet when connecting to another nameserver the
>  resolution is successful.
>
>  Hupping the local nameserver does not correct the problem.
>
>  Restarting the nameserver does correct the problem.
>
>  When the problem arises an nslookup type=ns returns the name of a valid
>
>  nameserver for the domain, but it will not return the IP.  After the
>  nameserver restart, both name and IP are turned on the ns query.
>
>  Any solutions or tricks to get around the problem?
>
>  Thanks!!