Jim Hague wrote:
> Mark Harrison wrote:
>> o BIND is configured and running correctly. It has one zone for my internal
>> network (overkill. I know:) and caches for the rest of the world.
>
> That's where we differ.
> Mine starts dialling pretty much immediately. Can you check nothing is trying
> to do a name lookup *during* the dialout process, 'cos that I imagine would
> have to time out before dialup completed. Which might take a couple of minutes.
This suddenly reminded me of a problem I'd had a while back.
Intermittently, I'd have delays of about two minutes before my computer
would dial out. I'd basically have a system running fine for a week or
two; I'd reboot to try a new kernel or play a DOS game, and when I'd
reload Linux, diald'd dial slow. That would last basically the whole
load, unless I killed named, which would fix it. Next boot, everything
would be fine again.
I tracked it down to the line being busy when I started up the system,
such that named didn't get to check on the root servers. Not knowing
about forwarders at the time, I eventually set my system up such that my
ip-up script would restart named. Setting forward-only works better.
Ed
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
