Netscape slow startup (was Re: [plug] PPP on demand)

[Colin Muller]

Colin Muller wrote:

> However, using 127.0.0.1 as the nameserver and setting up the correct
> forward and reverse name resolution for the local domains/IPs (in my
> case 127.0.0.* and 192.168.1.*) completely cures the Netscape startup
> problem.

Sorry, scrap this - further experimenting proves it wrong. What does
seem to work, however, is shutting down the local named completely, then
starting Netscape, then restarting the named. A hassle. Using tcpdump
suggests that on startup, NS looks for some of the root DNS servers -
not sure why. If the local named is not running, NS gives up instantly -
otherwise it waits for named to report failure, which is where the wait
comes in.

I'm still fiddling with this in between other things, will report any
progress and would appreciate any progress reports from others.

Colin