An efficient way to configure DNS on any system is to follow the steps given below carefully.
- Gather information.
- Collect the information you need to create the zone files. This task includes choosing a domain name for your network.
- Prepare zone files. As you prepare your zone files, remember that each zone must have an SOA record. Also, remember that forward and reverse zones each need name servers, and so their zone files must have NS records.
- Kill the name server process
- Prepare the named.boot file. Once you have killed the name server process, you can then create (or edit) the named.boot file.
- Start the name server process
- Configure the DNS Clients
To configure a UNIX DNS client, you need only to alter the /etc/resolv.conf file for each host that you want to participate in the domain.
DNS problems: Finally, remember not to get too ambitious as you first work with BIND. Take each step one at a time, and work slowly. Document each
move. Work in this way, and you will control the risks of establishing a DNS server.
In the next several lessons, we will work through these steps in detail. Along the way, you'll practice the steps with simulation exercises in
which you will set up a primary DNS server and a number of secondary servers.
This information applies To: Windows Server 2008, Windows Server 2008 R2
When a new Domain Name System (DNS) server is not installed on a domain controller, you typically perform the following tasks to configure it:
- Create a forward and (optional) reverse lookup zone.
- Determine whether the server will allow dynamic updates, including whether nonsecure updates are allowed.
- Determine whether queries will be forwarded and to what servers.
Instead of configuring these settings, you can choose instead to configure the server to use root hints so that you can perform these configuration tasks at a later time.