On Mon, 2005-04-04 at 13:47 +0100, Nigel Wade wrote:
> I would start by looking at nscd. It's responsible for caching all sorts of
> info on the client and quite often gets itself very confused.
>
> The 'host' command queries DNS directly without referring to nscd, whereas
> the resolver library will use nscd if its running. If your DNS server fails
> to resolve an entry this failure is cached by nscd (by default for 300s).
> So, a 'host' command might return a valid response whereas any attempt to
> contact it via the resolver/nscd would fail.
>
> Next time this happens, try flushing the nscd hosts cache:
>
> # nscd -i hosts
>
> and try again.
Bingo; that was the answer. I guess I have something new to read up
on tonight!
Thank you so much!
--
Those who entrust life and limb to Microsoft deserve neither. -Me, 2005
------------------------------------------------------------------------
Brian Fahrländer Christian, Conservative, and Technomad
Evansville, IN http://www.fahrlander.net
ICQ: 5119262 AIM: WheelDweller
------------------------------------------------------------------------
