One other important note: the modifications made with nsupdate take effect immediately on the DNS master server (and they also get pushed from there to slave servers), but they are not written immediately to the actual DNS zone file on disk on the master server.
authoritative; # Use this to send dhcp log messages to a different log file (you also # have to hack to complete the redirection). I don’t think that they are that bad and personally I don’t have any problem editing them after that bind has rewritten them.
I’m not sure how often that bind rewrites these files, but at least it seems to always happen when you stop the bind service.
I'd like to avoid having to "rndc freeze && rndc thaw" for fear of missing a dynamic update from the DHCP server.
Does anyone know how to get the updated records synchronized between views more effectively/efficently, or can shed some light on where I may be going wrong? ( 2009025039 ; serial 900 ; refresh 15 600 ; retry 10 86400 ; expire 1 day 900 ; minimum 15 min ) NS ns1. $TTL 30 AEGIS A 10.2.1.60 TXT "31bdb9b3dec929e051f778dda5abd0dfc7" $TTL 86400 ts-router A 10.1.1.1 A 10.1.2.1 A 10.1.3.1 A 10.1.4.1 A 10.1.5.1 A 10.1.6.1 A 10.1.7.1 A 10.1.8.1 A 10.2.1.1 A 10.2.2.1 A 10.2.3.1 ts-server A 10.2.1.20 ts-squid0 A 10.2.2.20 ts-squid1 A 10.2.2.21 $TTL 600 tssw4 A 10.2.3.4 tssw5 A 10.2.3.5 tssw6 A 10.2.3.6 tssw7 A 10.2.3.7 ; wash rinse repeat for more hosts $TTL 30 wintermute A 10.2.1.61 TXT "003f141e5bcd3fc86954ac559e8a55700" Different views act separately, it's essentially a convenience over running separate instances of named.
Information 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. 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.
Here's the quick and dirty: On BIND9 with a dynamic zone that's shared between views, doing a nsupdate, updating/creating/deleting a record will work fine if I query for that record from a client that falls into the same view I did the nsupdate from.
Querying from a view that the same as the one I used to nsupdate will throw NXDOMAIN (if adding a new record) or will show old record information in the event of a change/update until some arbitrary length of time (say 15 minutes) passes, or I forcibly do doesn't appear to do anything at all to resolve the issue -- I was hoping it was just a journal file thing since the journal flushes are documented to flush around 15 minutes.
Even though my DNS is automatically updated when it changes, via the highly versatile ddclient package, the traditional dynamic DNS update protocols (including dyndns.org's) are typically site-specific and non-standard.