This has been tested on 1999090311 and 1999090209 builds, on both Windows 95 and Windows NT 4 Workstation. What should happen: * Mozilla should load the Slashdot home page and all its images What actually happens: * Mozilla loads the home page, but none of the images are loaded. Other comments: Slashdot recently updated its server to a new IP address. While the DNS changes are propagating through the network, all the images on Slashdot are referenced using IP addresses, for instance, http://209.207.224.222/title.gif instead of using a DNS name for the server. This also happens for any URL entered in the URL bar using an IP address instead of a DNS name. For instance, entering http://207.200.73.41/ instead of http://www.mozilla.org/ will also cause the problem.

I can verify the slashdot behaviour on linux but not on mozilla.org. All is working well there for me when using the IP address.

Ok. This made me get out the network monitor and investigate further. What appears to happen is for IP addresses, Necko sends out a reverse IP lookup request something like: 222.224.207.209.in-addr.arpa. If the lookup succeeds, such as for Mozilla.org, all proceeds normally. If the lookup fails, then Necko will not load the IP address. None of the other browsers I tried (Netscape 4.5, IE 4.01) appear to do this reverse IP lookup. Why would Necko need to do this? Changing summary to reflect the problem more accurately.

*** Bug 13195 has been marked as a duplicate of this bug. ***

Necko doesn't recover from this. Anyone know how that behaviour can be explained?

looks like a dup, please add yourself to the cc: list on 12748 if you are interested in tracking its progress *** This bug has been marked as a duplicate of 12748 ***

Bulk move of all Necko (to be deleted component) bugs to new Networking component.