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.
If you’re an experienced Windows system engineer, they may seem a little trivial.
But even the most highly trained and savvy administrator can get in a hurry and make a mistake.
The default profile suggests that these files should be put in /var/lib/bind.
If you have followed the steps in my previous post you might have your zone database files in /etc/bind/zones.
Here is the zone declaration part of named.conf: zone "gilman.k12us" ; zone "20.172.in-addr.arpa" ; I've been looking at this all day. I am curious if your rev-zone shouldn't be 4.20.172.Edit: can you post applicable rev-dns portion of Reverse lookup works for the static IP addresses I have hand entered. The 172.20.0.0 network is for network devices, 172.20.2.0 is for wireless guest access, 172.20.3.0 is for students and 172.20.4.0 is for staff.