sometimes it resolves sometimes not

[Woger]

I found it! It was the secondary server. It wasn't upgrading the slave
zones for some reason. I deleted all the files and restarted named on
the secondary. After that everything worked fine.

Thanks for the help,

Roger

On Wed, 25 Feb 2004 19:59:23 +0000 (UTC), phn at icke-reklam.ipsec.nu
wrote:

>Woger <woger at berger.nl> wrote:
>> Hi there,
>
>> We have several servers running as webserver and also running named on
>> FreeBSD. All servers are running well but 1 server has a problem that
>> some of the domains on the server aren't resolvable for a few hours. I
>> can resolve the domains from all the servers in the ip range, but my
>> many ISP's don't resolve. After a few hours everything is working
>> again. I don't know where to search.
>
>> Roger
>
>Start in the /var/log/messages, see if anything is logged that coincidences
>with your disturbances.
>
>Whan the distrurbances occur, netstat -m tells you about memory usage,
>netstat -a about "current sessions". netstat -i shows NIC errors.
>
>Apart from that, more information might be handy, OS version, which version 
>of bind you use, contents of /etc/resolv.conf and named.conf and, maybe
>most importent, which domains that has trouble.
>
>Most likley you should continue this thread in "comp.unix.bsd.freebsd.misc" where
>freebsd specific issues are dealth with.