I'm seeing some strange things with our Primary and Secondary DNS servers,
on the same net, practically identical machines running v3.2c.
I suspect some sort of cache problem by what I'm reading in O'Reilly's
_DNS_and_Bind_.
Our primary DNS will give "server failed" while doing nslookups.
*** localhost can't find theweeds.smxcorp.com: Server failed
In daemon.log, I have several...
Feb 27 08:21:21 alpha named[20642]: ns_req: no address for rootserver
The secondary does the lookup just fine.
If I stop/start the Primary server the problem clears.
ALSO, after a few days, the symptoms switch to the secondary DNS.
>From the nslookup man page
Server failure
The name server found an internal inconsistency in its
database and could not return a valid answer.
How does one trace and fix this inconsistency? ..if that's really the
problem.
I dumped the databases but that didn't help much cuz I'm not sure how to
analyze it. O'Reilly's "DNS and Bind" just touches on the subject.
Sigh.
-Bill Sadvary
Dickinson College
Received on Thu Feb 27 1997 - 17:06:09 NZDT