Quoting "C.T. Paterson" <i [ dot ] adore [ dot ] my [ dot ] 64 [ at ] gmail [ dot ] com>:
Hey folks,
I'm trying to set up a DNS to resolve some of my own addresses within
my LAN. My addresses are served by a DHCP machine that is not a DNS,
and that I can not change. The addresses are predictable, though, so
I'm content for them to statically entered in my DNS.
You haven't mentioned how big your network is, nor if you are hosting
your own domain which needs to be reached from the outside. In either
case, if your network is small, my advise would be to avoid DNS
altogether for the internal network and rely instead on file based
address resolution via /etc/hosts on each machine on the local net.
Just name the internal IP addresses together with the hostnames
associated with it for each computer on the net. See man /etc/hosts
for details.
You might then only want to configure bind for two purposes: to act as a
caching nameserver (nice but hardly essential); or to act as the
authoritative nameserver for your domain, which is also not likely to
be necessary, since your ISP (or others like twisted4life.com) will do
it for you.
For most small-scale purposes, you really don't need to get yourself
into a 'bind'.
Michael
PS - If you are using a router which serves IP addresses via DHCP to the
localnet, you might want to see if it can do static IP assignment via
MAC address recognition. Basically, you teach the router to recognise
each computer by the MAC address of its ethernet card, and it always
serves the same IP address to that computer. No more IP address drift.
Check your manual.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.