|
|
The advice here didn't work for me, but this did...
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:
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. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|