I think that I would have done this if I would set this up in a corporate environment.
But for my own home network I really think that the /dev/urandom will be sufficient.
If you want to avoid the problem with bind rewriting the files and the need to freeze and unfreeze zones, then you could split your domains into two sub domains, for example lan. You could then have the DCHP server to only update the lan domain.
But I didn’t want this and I’m not going to update these files that often that it matters to me.
What I am trying to do is figure out how to get my server to update its DNS records via DHCP on the sonicwall. Would a better alternative be to place the server inline so it is acting as the DHCP server instead and act as a proxy between the sonic wall and the rest of the network?
Or can this be done so that the server sits on the same switch as the workstations?
3.1 Edit /etc/bind/local: # # Make sure to change the ddns update style to interim: ddns-update-style interim; ignore client-updates; # Overwrite client configured FQHNs ddns-domainname ""; ddns-rev-domainname ""; # option definitions common to all supported networks... subnet 192.168.0.0 netmask 255.255.255.0 The configuration files now contains our secret key. We also have to give the DHCP-server the permission to read and write it’s own file.
option domain-name "home.lan"; option domain-name-servers lan; default-lease-time 600; max-lease-time 7200; # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. 5.1 Remove the general read rights from the configuration files: The dns database files are now being rewritten by the bind service.
authoritative; # Use this to send dhcp log messages to a different log file (you also # have to hack to complete the redirection). Some people have mentioned that they think that bind messes up these files so that they are impossible to maintain.
There must be many more ways to troubleshoot any problems.
But I managed to get it working by checking the system log for clues when a service didn’t start or when the DHCP server didn’t update the DNS records: * Thanks to Phil who commented on the previous version of this guide with this tip on rndc freeze and unfreeze.