(Obtained as is from: The steps in this post shows how to configure the DHCP server to automatically update the DNS records when giving out a new lease to a client computer.
If you don’t have that I suggest that you first read my two other posts on how to install them: Setting up a DNS for the local network on the Ubuntu Hardy Heron server Setting up a DHCP server on Ubuntu Hardy Heron Step by step instructions Apparently the Ubuntu server is installed with an App Armor profile that prevents bind to write to the /etc/bind directory.
The default profile suggests that these files should be put in /var/lib/bind.
We can do this by using the DHCP service on a non-AD joined Windows Server configured with DHCP credentials, DHCP Option 015, and configured to force all leases to register into the zone whether the device has the ability to register on its own or not.
The credentials allows DHCP to own the record, so in case the device leaves and returns at a later date and gets a new IP, the DHCP service can update the old host record in DNS with the new IP.
Please let me know if you know of a better solution.