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.Since the DNS server won’t have a record of anything outside of your LAN, you’ll need to put your ISP’s or some other entity’s DNS server IP addresses here. Your DNS server will eventually build up a good cache of sites you visit regularly, but it still will often need to query external name servers.For the e-mail address, we use a dot instead of an @. ( 1263527838 ; serial 10800 ; refresh (3 hours) 3600 ; retry (1 hour) 604800 ; expire (1 week) 38400 ; minimum (10 hours 40 minutes) ) # Next, we define the hosts necessary to make the domain function. However, this time, # we're adding "PTR records", or pointer records. The file is organized into four sections: configuration directives, the DNS zones we’re allowed to update, the DHCP scope definition and scope-specific configuration directives, and DHCP groups; we’ll tackle them one at a time.# The lines after that define the zone serial number, which is used to keep track # of when the zone file was modified, and then some interval definitions which # you can leave as default. First, we add # an "NS Record" to define the domain's name server... # ..an "A Record" for the domain server's IP address... A cautionary note: pay extremely close attention to syntax, especially punctuation.I’d intended to bang the post out in a single evening, but instead it’s taken a couple of hours over three days to complete. ) This tutorial has been done more than once, to be sure.You can search around and find tons of other writeups about deploying DNS and DHCP and getting them to update each other.When installed from a package, the configuration files for BIND9 are located in (that’s “name-d”, as in the daemon controlling the naming service, not “named” as in the past tense verb), which really just functions as a container and references the other three configuration files: Default contents oflink1 2 3 4 5 6 7 8 9 10 11 // This is the primary configuration file for the BIND DNS server named. for information on the // structure of BIND configuration files in Debian, *BEFORE* you customize // this configuration file.// // If you are just adding zones, please do that in /etc/bind/local include "/etc/bind/options"; include "/etc/bind/local"; include "/etc/bind/default-zones"; As the file says in the comments, this isn’t the place to do any actual work.
In this post, we’ll set up DNS and DHCP on Ubuntu, and then configure them to work together. This blog entry ended up being bloody huge, because I don’t just list the configuration options to set but rather go into detail on what each one does.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.Here, we’re allowing the DHCP server (which we’ll also configure with the same key) to update the forward lookup zone and also the .0/24 reverse lookup zone.Before we add those zones into the configuration file, though, we have to also do some cryptographic voodoo.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.