namely, that it had a static IP address and a valid hostname.
This involved editing /etc/networks/interfaces to set the IP address of the primary ethernet interface (eth0): : I performed this step because of some odd issues I’ve had with systems suddenly switching to a dynamically allocated IP address even when I had specifically set a static one for the system.
The following guide describes what I did to get BIND9 and DHCP3-server installed, configured, and running on an Ubuntu 10.04 LTS system.
My second step was ensuring that my system was in a proper state to be a DNS/DHCP server…
The journal entries get applied periodically to the main zone file.
If you restart bind9, the journal entries also get applied.
Recently I have to figure out (again) how to get secure dynamic DNS updates working with nsupdate and Bind9.
It's going to get in our way, so we need to update a few things in bind in order to get it to play nicely with our journal files.I first saw nsupdate mentioned on the devops-toolchain mailing list as a tool for dynamically updating DNS zone files from the command line.Since this definitely beats manual editing of zone files, I'd thought I'd give it a try. I won't go into the details of setting up BIND 9 on Ubuntu -- see a good article about this here. There are lots of resources out there, but as usual it's hard to separate the grain from the chaff.When thinking of the security, it will be very, very stupid to allow anybody to update records.Luckily there doesn't seem to be a script-kiddie-proof -tool for doing that (or at least I haven't found one yet).While I won't be going over how to setup Bind9 in this article I will follow up with an article for properly getting that setup.