It was my difficulties with getting the DHCP server to automatically update the DNS server that lead me ask a question on the web site.Though I got no perfect answer, I was able to piece together enough to generate this working solution.I then upgraded to 8, which took some messing, and most recently to 9 - which was painless.

For the average home computer user there is no need to install a complex package such as the Internet Software Consortium's BIND DNS or DHCP server, since there are far simpler lower resource tools to use, for example dnsmasq.

For those who you wish to learn how to use ISC's BIND and DHCP, for example as a learning exercise, this is how I got it all to work in Debian Sarge, the current stable version of Debian GNU/Linux.

My DHCP server and DNS server are on the box, so here I am only allowing Here is my local zone details, suitably modified. By default the ISC DHCP3 server shipped in Debian Sarge does not do dynamic DNS update. # Normal DHCP stuff option domain-name "network.athome."; option domain-name-servers 192.168.0.60, 192.168.0.1; option ntp-servers 192.168.0.60; option ip-forwarding off; default-lease-time 600; max-lease-time 7200; authoritative; log-facility local7; subnet 192.168.0.0 netmask 255.255.255.0 This is a very good article, i've been wanting to set this up as a learning experience in my home network for some time.

Here I let BIND know which domains it can update; in my case I only have one domain to deal with. If your DHCP and DNS servers are on separate machines you need to copy the file between them or arrange for one machine to remotely access the file system of the other. I'm sure this question is answered once I get this set up.

Some of these machines i want on fixed ip addresses (various reasons) but I want them getting their information from dhcp, but i want to make sure that it won't hurt anything. For example machine with a hostname of foo contacts dhcp for the athome.network domain, this then gives it ip address ...100 and then there is a dynamic dns entry for foo.athome.network aaron Through correctness comes ease -Chiun -The Destroyer series So, i finally got around to doing this I had a few issues that were eventually resolved simply, but were a bit tedious to track down, since "no one is having this problem but me!

The more I think about it, the more it seems like I would just leave my static configurations the way they are, and just new machines (laptops) that come in and out of my network would possibly change ip address. " I had setup everything like the article says (i made some typos, but we don't have to cover that) but things weren't working and i couldn't find what I didn't do right.

To set-up DNS you need to set your domain rules as per normal BIND9 format.

BIND9 does have a reputation for being complex but you can find help in the pages which are complete, if very long, and there are good books to help you get through (see below).

I am also loading in the shared secret key in at this stage. But what happens with a static ip address i'm assigning through dhcp? Work's machine is not in my DNS, so it uses DHCP and it retains it's hostname, but is placed in the domain of the DHCP server, not work's.

Does it get the hostname from the dhcp config and then use that to update dns? aaron Through correctness comes ease -Chiun -The Destroyer series Static though DHCP? My static machines retain their hostname and fully qualified domain name as they ignore DHCP totally. Once it's in my domain, DNS know where it is and I can access it via it's hostname or FQDN. -- "It's Not Magic, It's Work" Adamyes, i mean a static reservation what i do is i have all my machines set to get their info thorugh dhcp.

For a simple home network the O'Reilly book and the man page should be all you need.