Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'The advice here didn't work for me, but this did...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
The advice here didn't work for me, but this did...
Authored by: briank on Jan 23, '07 04:28:02PM
A couple of dead links in this thread...but the topic is still alive and well, 6 years later into 10.3-10.4! There are actually a couple of things that must be done in combination for all this work. While niload will get your hosts file into NetInfo, if lookupd is using the cache (which is by default in 10.3.9), your changes may take hours to go into effect. Here's an up-to-date link that explains all the necessary changes:

http://aplawrence.com/MacOSX/macosxlookupd.html

The changes work as advertised, but only if you actually read the entire document and check your lookupd lookup order for Hosts (by default, DNS is consulted before NetInfo, so niload is useless if you are trying to resolve local domains locally unless you also change the order of lookup so that NI comes before DNS).

Important to note: At a minimum, you will need to flush your lookupd cache for any Host changes to NetInfo to take effect:

lookupd -flushcache

Also, consider using the -d switch with niload. Otherwise, multiple localhost entries in your /etc/hosts file (important for a number of internal operations and at boot time) won't make it into your NetInfo database.

[ Reply to This | # ]