On 11/23/2010 5:48 AM, Gerrard Geldenhuis wrote:
I believe this is down to system libraries but is there any way to make 389-ds aware of
changes in /etc/resolv.conf? In my test environment I have had to restart the dirsrv to
get get changes in resolv.conf take effect.
Specifically I can't initiate a new host using replication if the resolv.conf entries
is wrong... changing them requires a restart.
Apart from the whole debate about whether I should be changing /etc/resolv.conf at all or
during "production" ... any comments would be welcome.
Are you using a caching service like nscd? Sometimes that can result in
a negative hit for missed hostnames that can take a while to expire, but
it wouldn't be specific to 389. In that case "nscd -i hosts" will flush
the cache and things will start working.