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: cdbaby on May 23, '02 04:34:57PM
I was psyched to find this thread, but for some reason, using the graphic NetInfo manager didn't work for me. Even tried rebooting but my changes didn't stick.

BUT - found another page on the subject here that does work:

http://quigley.durrow.com/hostsundermacosx.html

His advice seems a little strange, and I admit that I don't understand it, but it DOES work for me, whereas the other things mentioned here didn't, maybe because I'm trying to force a domain name for a box across the room like this:

192.168.0.5 testdomain.test
192.168.0.6 anotherdomain.test

SO FIRST - go EDIT your /etc/hosts file the way you would under Linux or BSD. (like the above.) Add your entries there.

THEN - go follow that weblink above and do his advice. It works.


[ Reply to This | # ]
get TMA
Authored by: ppmax on May 24, '02 01:35:01AM

The Moose's Apprentice (TMA) is a great little tool that does many things for you...including fixing an issue with the lookupd order.

get it at www.wundermoosen.com

just for reference my osx box:
sits behind a router on an internal lan
can be accessed by any of 3 different IP addresses and domain names
serves two public websites (apache virtural domains)
working inbound and outbound sendmail (tied to one of my domain names)

i believe most of the issues people have can be fixed by downloading ad installing TMA. for the adventurous, you can fix the lookupd order by hand.

open up netinfo manager and add an entry called locations
check out this picutre for reference:
http://homepage.mac.com/ppmax/locations.jpg

good luck




[ Reply to This | # ]
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 | # ]