Re: [tlug] Restarting a dead DNS lookup

["Stephen J. Turnbull" <stephen@example.com>]

>>>>> "Jim" == Jim Breen <Jim.Breen@example.com> writes:

    Jim> Sound like we're getting somewhere. However I can't see that
    Jim> I actually have nscd running. ps doesn't pick it up, and
    Jim> there is no sign of it on the messages at boot time where it
    Jim> reports xinetd, crond, etc. being started.

    Jim> The comment at the front of /etc/rc.d/init.d/nscd implies it
    Jim> doesn't start by default:

That's the bug.  :-)  However, in turns out to be relatively recent
(Red Hat 9 or so).  But go ahead, try starting ncsd by hand anyway.

>>>>> On Thu, 13 Nov 2003 17:23:37 -0500,
>>>>> Jan Harkes <jaharkes@example.com> wrote:

    Jan Harkes> On the other hand there is a libc/resolver problem on
    Jan Harkes> RedHat 9, maybe other systems as well. According to
    Jan Harkes> the manpage, using anything like res_query or
    Jan Harkes> res_search will implicitly initialize the
    Jan Harkes> resolver. However on RedHat 9 this doesn't happen
    Jan Harkes> (correctly) and in fact leaves libresolve in a badly
    Jan Harkes> configured state.

    Jan Harkes> What I noticed was that it would only send queries to
    Jan Harkes> a locally running nameserver cache daemon and never
    Jan Harkes> actually try to talk to the configured DNS
    Jan Harkes> servers. The solution on that particular machine was
    Jan Harkes> to simply start nscd as root, and it will run in the
    Jan Harkes> background and handle the name lookups correctly.

    Jan Harkes> So as root, start the 'nscd' binary and venus might
    Jan Harkes> just start working again.



-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.