Bind 8.2.2-P5 Mystery - HELP

[Mohammed Ghanawi]

More mysterious findings .... This is an update on the last problem I
posted, I hope someone
knows what the problem is.

Also now the secondary servers which are running Version 4.9.4 of bind,
are failing on some zones
as a result, the outside world can not see our domain anymore, since the
zones have expired.

I just upgraded to bind 8.2.2-P5, and man I am having strange problems
...

Every now and then my new bind 8.2.2-P5 named just refuses to resolve
local
addresses, it still resolve addresses outside our domain with no
problem. When this problem happen all clients fail to access any
Internet
services. What is more strange, on the server itself I can resolve the
local domain and remote domain addresses. From the clients I can ping
machines locally by IP address but not by name, and I can ping remote
machine both by name and IP address. I tried stopping named and
restarting but no success, I even rebooted the whole machine. Plus even
more strange, on any client that refuses to ping a local machine by name

if I run nslookup on that client it connects to the correct DNS server
and resolves names (from within nslookup) with no problem, once I am out

of nslookup and try to ping local clients by name it fails with the
message UNKNOWN HOST (This happen to all clients using that DNS server).

After sometime everything is back together and clients starts resolving
both local and remote hostnames with no problem. There is nothing in the

log files either.

I am running Solaris 2.6


-- Binary/unsupported file stripped by Listar --
-- Type: text/x-vcard
-- File: mohammed.ghanawi.vcf
-- Desc: Card for Mohammed Ghanawi