You should find lines similar to these, in the system logs on both machines: If OMAPI is working properly you can test failover by stopping the primary server.
If you are using a firewall, you will need to open TCP ports 6 Once you are sure everything is working as expected, restart both servers to ensure everything is running correctly.
If you have followed the steps in my previous post you might have your zone database files in /etc/bind/zones.
We will start by copying the files so we have a backup remaining if anything goes wrong: 1.1 Copy the zone database files: We now need to add the key to the bind configuration and tell it what zones that we want it to allow updates on.
Before continuing These steps assumes that you already have a working copy of dhcp3-server and bind9 installed.
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.
I have a small network setup and I cannot get DNS to work.
DHCP is functioning normal and working fine but it cannot update the DNS pointers for some reason. ----------------------- ddns-updates on; ddns-domainname "mydomain.lan"; ddns-update-style ad-hoc; allow unknown-clients; option domain-name "mydomain.lan"; option domain-name-servers 192.168.0.1, 22.214.171.124; option routers 192.168.0.1; option ntp-servers gov; option netbios-name-servers 192.168.0.1; option netbios-dd-server 192.168.0.1; option netbios-node-type 8; authoritative; default-lease-time 172800; subnet 192.168.0.0 netmask 255.255.255.0 Jul 22 NIKKI named: the working directory is not writable Aug 11 NIKKI dhcpd: if The Beast.IN A rrset doesn't exist add The Beast.86400 IN A 192.168.0.210: timed out.