So it seems that the DHCP and BIND packages have a function coded into them that allows the former to update the latter on-the-fly called ddns-update-style in the dhcpd.conf file and allow-update which goes into the named.conf or named.conf.local configuration file depending on your setup.
My first search turned up this page, which gave a rough outline of how one would implement the ddns and allow-update options. This wasn’t really enough for me so I decided to go looking a little further. Some more searching brought me to the Debian DDNS page. I knew I could use this regardless of which distro I was using for a server simply due to the fact that the internet is such a standardized sector of computing, especially on the topic of DHCP and DNS.
Using the information I have, I’ll be setting up a closed network of Virtual Machines.
Here’s an outline of the virtual machines and their purposes that I’ll be using:
- Firstly we have the DHCP server which will be running on Ubuntu Server 16.04 LTS.
I’ve found that, for some reason, that Ubuntu Server handles the DHCP requests more reliably compared to CentOS.Fresh VM cancels out what’s written just before this but I’ll stick with Ubuntu Server for the purpose of getting a well-rounded experience.
- That said, the DNS server will be running on CentOS Linux 7. The last number in the ISO name is 1611 so I imagine that’s the build number, if that gives anyone a good idea. I’ve chosen CentOS simply because I’m more familiar with it.
- Lastly, I’ll have several clients requesting IPs from the DHCP server. These clients will include Windows 7 (I already had one for Office and Multisim purposes), Slackware (my course requires knowledge of this due to it’s fine-grained tuning requirements), Ubuntu, Fedora, and lastly Arch.
I don’t estimate this taking much too long so I should have this up and running within the next few days. In the final report, I’ll be detailing all the configuration options I took and how you can replicate this experiment.