We're using Ubuntu 10.04.4 LTS, x64 (on Amazon AWS).
No NSCD
David Kohen
Waze IFS team.
Date: Wed, 2 May 2012 11:18:59 +0200
From: Martin Pala <address@hidden>
To: The monit developer list <address@hidden>
Subject: Re: [monit-dev] Resolver issue
Message-ID: <address@hidden>
Content-Type: text/plain; charset=iso-8859-1
Hello David,
monit doesn't cache the resolved names nor nameservers - it uses the (libc's) getaddrinfo() interface to resolve the hostnames when necessary. Please can you provide more informations about the system so we can try to replicate the problem? (platform, OS, version). Do you use nscd? (name service caching daemon)
Regards,
Martin
On May 1, 2012, at 1:44 PM, David Kohen wrote:
> Hello,
> We had an issue with our primary internal DNS server, we had to replace it.
> I have notices that a heartbeat check is taking about 5 seconds whereas on other servers, it was in the area of 0.01 seconds.
> After a restart of the monit daemon, it did the heartbeat in 0.016 seconds, which made me realize that the daemon is caching the nameservers to speed up lookups, but this makes it difficult to do changes in the nameservers without restarting the daemon.
> Could this behavior be changed or is it something that could never be changed?
>
> David Kohen
> Waze IFS team.
>
> _______________________________________________
> monit-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/monit-dev
------------------------------
_______________________________________________
monit-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/monit-dev