It's not too complicated -- a couple zone files, with about
5-10 lines + number of machines in each, and some minor
customizations to named.conf. Unfortunately, BIND is big &
complicated software. Getting it wrong is easier than getting it
right, and bad DNS records may work, but cause problems for other
people on the Internet.
The easiest thing is probably to have your ISP set up a few
DNS records for you. The latency of asking querying their DNS servers
instead of one on your LAN will trivial. Alternatively, you could use
a DNS service like EasyDNS.
If you don't really need DNS service, you might be able to
get by with hosts files. Add a few lines like this into /etc/hosts,
and then copy it to every machine. Mac OS X (and most UNIXes and
Windows) consult host files before trying DNS lookups.
10.0.1.1 speedtouch
10.0.1.250 printer
10.0.1.251 imac
This assumes you're using static addresses; dynamic DNS (if
you aren't) is much more complicated.
All that said, if you really want to use DNS on Mac OS X,
it's a fairly standard BIND install. Mac OS X Server (which might be
nice for a small home office anyway, but costs more than client) has
a decent GUI for enabling & configuring DNS and maintaining zone
files. If you're doing it on client, read a few of the many documents
on BIND 9 -- pretty much everything they have to say is relevant. I
suggest you *not* publicize your private domain on the Internet --
this reduces the likelihood of lame delegations and other problems,
and avoids the official requirement for a backup (slave) name server.
Assuming you have bbedit, try "more /var/named/*; bbedit -u
/etc/named.conf /var/named/local.zone
/var/named/0.0.127.in-addr.arpa". Copying the samples, create new
pointers to forward and reverse zones, then following the examples
and online docs, create & populate your own private forward & reverse
zones.
Use named-checkconf & named-checkzone.
Good luck,
-
Chris Pepper: <
http://www.reppep.com/~pepper/>
Rockefeller University: <
http://www.rockefeller.edu/>