busy-bee.net buzz buzz buzz goes the honeybee home | blog | links | about me

linux to an imac

2002-07-17 14:43 / useless but educational  »

just like my degree ...

I was trying to change my DNS config on the command line (why? because I'm not in front of my machine), and didn't even consider that the UN*X or at least FreeBSD and Linux standard of /etc/resolv.conf would be used by OSX. Not an unfounded assumption, given e.g., the comments at the head of /etc/hosts.

Anyway - it is used, but - weh-hey - it doesn't have to be! You can use a netinfo database instead. Try a nidump -r /locations/resolver / to see what, if anything, you've got there already. If nothing, then create a new path with niutil -create / /locations/resolver. Add keys with niutil -createprop / /locations/resolver nameserver <your nameserver> and niutil -createprop / /locations/resolver domain <your domain> if you want to search a domain as well. (If you need more than one DNS entry, it looks like niutil -appendprop does the job.)

To test it: move /etc/resolv.conf somewhere else, and send a SIGHUP to lookupd with kill -HUP `cat /var/run/lookupd.pid`. Then ping some computer or other and see that the name resolves.

Hopefully the network system preferences pane should pick these changes up .. I just need to get home and check. And one day maybe I'll tweak the cache settings in lookupd, which is sometimes a little sluggish (that might be my ISP though).

mod_perl -- Speed, Power, Scalability