Having a reverse DNS record for your domain will prevent email originating from your domain from getting immediately rejected.RDNS can also be very useful when tracking down network issues and was the original driving force of RDNS.For example, in IPv4, you could have a /23 network registered with ARIN that is comprised of two /24 delegations.In this case, you are able to delegate one set of nameservers to the first delegation and another set of nameservers to the second delegation. Occasional users can manage their delegations via ARIN Online, but users who manage a large number of delegations can programmatically modify their delegations using ARIN’s RESTful provisioning system.basically, you need to create an RNDC key and a assign that RNDC key updateable access from your pc.here is how to do it: 1) create your RNDC key by using the dnssec-keygen command. the command is: $ dnssec-keygen 2) In your file, add the following lines: # Start controls ; # Change /etc/bind to the path of your named/bind directory include "/etc/bind/rndc.key"; ....When pinging a website or IP address, one part of the output is the server’s RDNS record.When you enter a domain name into your browser, the DNS system will find the IP address of the server the domain is associated with. It establishes what domain is associated with the IP address.
(the other subnets are configed the same way) zone gilman.k12us. subnet 172.20.0.0 netmask 255.255.255.0 the reason it isn't 'authorising' (as the syslog says) is that you need to have a shared key that both bind (or your dns system) and dhcp-server (or your dhcp server) can share so that they can verify that they are asking each other to update each other.Also, the more experience you have, the more likely you are to make your DNS infrastructure complex, inviting the attention of Mr.Murphy and other elements of chaotic cosmic calamity.ARIN’s delegation management tools enable you to individually manage each reverse delegation within both IPv4 and IPv6 networks.Delegations can be managed in IPv4 on bit boundaries (/8, /16 or /24s), and IPv6 networks can be managed on nibble boundaries (every 4 bits of the IPv6 address).