I've noticed this behavior with both Mozilla and Firefox on Linux. Each time either of these is started they do a DNS lookup of the local hostname. Of course my ISP's DNS server returns a lookup failure and I've seen that FF tries each nameserver once and then does a lookup of the home page and that succeeds. Mozilla did the same thing and hits each nameserver three times before failing (I have the startup page to be blank).
Is this behavior just a way to test for a network connection? If so, why not look up www.mozilla.org which would at least return a valid IP address? If it is trying to learn the local IP address, there are better ways to do this, I would think, but what benefit exists in that information? I recall that old versions of Netscape (on Linux at least) would freeze for a bit if started without a network connection as it was doing a DNS lookup. It seems like this behavior is some kind of holdover. Mostly, I am curious about the behavior and am trying to clean up unnecessary network traffic from my systems. - Nate >> -- "The optimist proclaims that we live in the best of all possible worlds, the pessimist fears this is true." _______________________________________________ Mozilla-netlib mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-netlib
