User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030210 When trying to connect to sites on my local machine while not connected to the network, I cannot. I get errors about sites not being found. The sites were setup in NetInfo and apache and they do work in other browsers at the time they are not working in Mozilla (internet explorer, safari, chimera). If I load the site in Mozilla before disconnecting from the network, they continue to work until I quit Mozilla even after disconnnecting from the network. Reproducible: Always Steps to Reproduce: 1. Quit Mozilla Completely 2. Disconnect from network (unplug ethernet or turn off airport) 3. Try to go to a local site as defined in netinfo/machines 4. Site Not Found error in Mozilla. Other browsers work fine. 5. Connect to network again and it still doesnt' work 6. Quit Mozilla and start again and if does work Actual Results: I get an unable to connect to site, site not found error. Expected Results: look up the local name and connect to localhost with the appropriate vhost name. This worked correctly in Mozilla 1.2.1. It works in IE, Chimera and Safari. It's almost as though Mozilla is using a non-system call to resolve the dns. Since I do a lot of local web development offline, this makes Mozilla unusable as my main development browser.

I was doing some additional searching and I think this bug is really 192589 in disguise.

*** This bug has been marked as a duplicate of 192589 ***

This bug sounded similar to Bug 192589 but it turns out that it isn't. Currently, I'm running "Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4a) Gecko/20030228". Bug 192589 indeed seems to be fixed, that is, if I start mozilla when disconnected from the network, after reconnecting to the network connections will work. However, when disconnected from the network, local machine names stored in NetInfo do not resolve correctly. I have numerous machine names setup in netinfo and apache serving vhosts based on them. All of these work when mozilla is connected to ethernet with available DNS servers. When disconnected, mozilla doesn't work with these hosts while other browsers including Safari, IE, and Chimera do work. It's as though mozilla isn't using the native system calls for resolution, but trying to connect to a DNS server.

-> new Based on what you have described, there does seem to be problems with name resolution (once you access a site by DNS, the browser will remember the IP address and not go back to the resolver). I had not considered the implications of NetInfo for mozilla's name resolution. Can you provide a testcase that describes your configuration (w/ steps that show how you added stuff to netinfo and how you viewed it w/ line command utilities?) I haven't used NetInfo since NeXTSTEP 2.x, so I know what you are talking about, but not how to do it in Mac OS X.

There is a short article here about how to setup machine names in OSX under NetInfo. It is basically the MacOS way to use a hosts file. <http://www.evolt.org/article/comment/18/13138/> Here's a more command line sort of way (you must be root or use sudo): niutil -create / machines/fly.ing.quetzal niutil -createprop / machines/fly.ing.quetzal ip_address 127.0.0.1 niutil -createprop / machines/fly.ing.quetzal serves ./local Now setup an apache host: vi /etc/httpd/httpd.conf In apache, you need to uncomment the NameVirtualHost directive and set to 127.0.0.1: NameVirtualHost 127.0.0.1 Then setup a vhost as so: <VirtualHost fly.ing.quetzal> ServerAdmin paul@burney.ws ServerName fly.ing.quetzal DocumentRoot /web/quetzal </VirtualHost> (Making sure that DocumentRoot points to a real location) Restart apache: apachectl configtest apachectl restart Point a browser to the location: http://fly.ing.quetzal/ lynx fly.ing.quetzal And you should see the directory contents/index page of that directory. I remember that in previous versions of OSX, you had to manually setup an /etc/lookupd/hosts file and then populate it for netinfo to work correctly with local machine names. Mine looks like this: LookupOrder = Cache FF NI DNS NIL ValidateCache = NO When I do an `nslookup` for the fake domain on the command line `nslookup fly.ing.quetzal`, it fails, but browsers pick it up just fine. When not connected to the network, other browsers still find it just fine, except Mozilla 1.3b/1.4a (1.2.1 worked, if I recall correctly). Hope that helps.

dns -> gordon.

One more site with a bit more detail about NetInfo, without getting into the Apple developer docs: http://www.macwrite.com/criticalmass/mac-os-x-hosts-jaguar.php

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

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

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

There was some issues w/ specific Mac OS X versions and resolver APIs...

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

Summary: Started after 1.2.1 and 1.3a. Possibly CFM->Mach-O related, because affects 1.3b-> including Chimera 0.7 and Firebird 0.7. Most recent report was in 1.5a. There were some Mac OS NSPR changes in 1.3f, that sounded related, but reports still came in. However, no recent reports since then. Darin, any ideas?

The bug seems to be solved in Mozilla 1.6 on OsX 1.3 (Panther). I can confirm the bug on Moz 1.4.1, so the upgrade from OsX 1.2 to 1.3 did not affect it, apparently. I skipped Moz 1.5 - let me know if you need a test on that one too. Thanks a LOT to whoever fixed it ! Now I can work at home a few days a week :-))

marking wfm based on comment #14