On Mon, 2005-04-04 at 23:36 +0200, Jean Francois Martinez wrote:
What could be happenning is that your ISP is rotating his machines on
DNS and sending your notifications through DHCP. But you have a static
configuration for named so it is pointing at machines who for some
reason don't have up to date data. You have to read the DHCP
documentation in order for it updating your named config, and, very important, firewall config and then restarting both.
No, I'm on a static IP, and the problem was two different applications not sharing the same information- "host" could find it in a flash, but Firefox wouldn't...even immediately after it.
Thankfully, "ncsd -i host" on the command line nailed it.
Thanks, though!
Given that nscd is the "problem", you can alter the time for which nscd caches failed DNS lookups. In /etc/nscd.conf change the timeout value in
negative-time-to-live hosts 300
to a smaller value than 300 seconds.
--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : nmw@xxxxxxxxxxxx
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555