Configure the forward and reverse lookup zones for dynamic updating


31-Jul-2017 22:42

To do this, run the following command: 1 /usr/sbin/rndc-confgen -a This will create a file named , whose contents will look something like this: rndc.key1 2 3 4 key "rndc-key" ; Copy this file to the clipboard, as we’re now reqdy to configure our DNS zones, and the very first thing to put into the config file will be the contents of for editing and make it look like this: /etc/bind/local1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 key "rndc-key" ; zone "bigdinosaur.org" ; zone ".in-addr.arpa" ; zone "facebook.com" ; This defines the three zones we need.

The first zone is my forward lookup zone for Bigdinosaur.org, and the entry tells the DNS server that the IP addresses for all host names ending in “bigdinosaur.org” can be found in the file section is allowed to make modifications to that zone.

We need to dive into section contains servers that the DNS server will check if it doesn’t have a record of the host you’re trying to reach.

This whole exercise of building zones is kind of pointless without ; that is, without the ability of the DHCP server to update the DNS zones with the addresses it hands out and the host names those addresses are assigned to.

So, we need to generate a cryprographic hash which the DHS and DHCP servers both have access to.

There are lots of options, but it’s easiest to just pull out the big guns and set up BIND9, the current version of the DNS software that powers the Internet, along with the ISC’s DHCP server.

DNS and DHCP are like peas and carrots, as the saying goes—DHCP hands out the addresses, but doesn’t communicate to other network hosts who has what address; DNS knows how to correlate names to addresses but doesn’t hand out addresses itself.Now that the zones have been created, we’ll need to populate them with basic data, as well as the IP addresses and network names of any statically-addressed hosts on the network. # # # Now we're ready to begin adding hosts, but first we need another origin # statement to indicate that the hosts added below originate not from ".", like # the domain itself; rather, they originate from "bigdinosaur.org". As indicated above, the first part of the file defines basic info about the zone, and the second part defines the hosts.Don’t worry about filling in the names for any DHCP-assigned hosts, as the dynamic update setting we’ve just finished with will take care of allowing DHCP to add in its own hosts without you having to deal with it. Each statically-addressed host gets an A record so that the server knows how to correlate its name with its IP address. The thing to notice about the reverse zone is the name of the domain we’re working with: is used as the domain for reverse lookups for historical reasons, because DNS reverse lookups use a method codified back when was actually a working domain.You can search around and find tons of other writeups about deploying DNS and DHCP and getting them to update each other.