Home > Articles > Microsoft > MCSE

This chapter is from the book

Configuring DNS

Several configuration issues need to be considered when setting up DNS. These include the following:

  • Root servers

  • Forward lookup zones

  • Reverse lookup zones

  • Resource records

  • Dynamic DNS

Root Servers

When you initially launch the DNS Microsoft Management Console (MMC) snap-in after installing the DNS service, a configuration wizard opens. You initially have the option of configuring your server as a root server. Root servers on the Internet are authoritative for the entire DNS namespace. Obviously, you would not be able to create a root server that is authoritative for the entire Internet, so you should only create a root server if your network is not connected to the Internet. If your LAN is not connected to the Internet and you create a root server, the root server is authoritative for any namespace you create in the AD forest.

Forward Lookup Zones

For DNS services to work, at least one forward lookup zone must be configured on your server. The reason is that forward lookup zones are what enable forward lookup queries, the standard method of name resolution in DNS, to work. Forward lookup zones allow computers to resolve host names to IP addresses.

To create a forward lookup zone, right-click Forward Lookup Zones in the DNS MMC console and click New Zone. A configuration wizard launches.

The first choice you have to make when configuring a new zone is what type of zone it will be. The choices are as follows:

  • Active Directory integrated

  • Standard primary

  • Standard secondary

The zones correspond with the types of name servers discussed previously in this chapter. If you have not installed AD yet (which isn't required for DNS), the AD integrated option will be grayed out. In many cases, it is easier to configure DNS before installing AD, then create the zones as primary and secondary zones, and finally convert them to AD integrated zones after installing AD. The reason is that installing both at the same time requires configuring two major services and significant network changes simultaneously. Instead, you should take on one task at a time, which makes troubleshooting much easier in the event of problems.

Unless you have a need to communicate with non-Windows 2000 DNS servers, you should use AD integrated zones whenever possible.


You need to know when to use one type of AD integrated zone versus another.

Reverse Lookup Zones

A reverse lookup zone is not required for DNS services to function; however, you will want to create a reverse lookup zone to allow reverse lookup queries to function. Without a reverse lookup zone, troubleshooting tools such as NSLOOKUP that can resolve host names from IP addresses cannot work. Whereas forward lookup zones allow computers to resolve host names to IP addresses, reverse lookup zones allow computers to resolve IP addresses to host names. As with forward lookup zones, you have the option of creating AD integrated, standard primary, or standard secondary zones.

Unlike naming a forward lookup zone, you name a reverse lookup zone by its IP address. You can either type your network ID into the first field and watch the reverse lookup zone name automatically be created for you, or you can choose to type in the reverse lookup zone name into the second field following RFC conventions. The information text between the network ID and reverse lookup zone name fields describes how to name a reverse lookup zone.

As with forward lookup zones, if you are creating an AD integrated zone, you are done after supplying the zone name. With standard primary and standard secondary zones, you have to also supply the zone filename, which defaults to adding a .dns extension onto the end of your zone name. With a standard secondary zone, you have to list the IP addresses of the primary DNS servers with which the secondary zone should communicate.

With your zones configured and DNS services functioning, let's look at the entries, known as resource records, you'll find within the server.

Resource Records

Resource records (RRs) are the basic units of information within DNS used to resolve all DNS queries. When the Windows 2000 DNS service starts up, a number of records are registered at the server.

Several common RRs are used with Windows 2000 DNS:

  • Start of Authority (SOA)

  • Name Server (NS)

  • Address (A)

  • Pointer (PTR)

  • Mail Exchanger (MX)

  • Service (SRV)

  • Canonical Name (CNAME)

Start of Authority Record (SOA)

The SOA record is contained at the beginning of every zone, both forward lookup and reverse lookup zones. It defines a number of details for the zone, including the following:

  • Time-to-live (TTL)—The amount of time a record is considered valid in the DNS database. Higher values reduce network bandwidth utilization but increase the possibility of outdated information existing.

  • Authoritative server—Shows the primary DNS server that is authoritative for the zone.

  • Responsible person—Shows the e-mail address of the person who administers the zone.

  • Serial number—Shows the serial number of the zone. Remember that the serial number is incremented whenever an update is made and that secondary servers use serial numbers to determine whether their copy of the zone database is out of date.

  • Refresh—Shows how often secondary servers check to see whether their zone database files need updating.

  • Retry—Shows how long a secondary server will wait after sending an AXFR (full zone transfer for standard zones) or IXFR (incremental zone transfer for standard zones) request before resending the request.

  • Expire—Shows how long after a zone transfer that a secondary server will respond to zone queries before discarding the zone as invalid because of no communication with the primary server.

  • Minimum TTL—Shows the minimum TTL a resource record will use if it does not explicitly state a TTL value.

Name Server (NS) Records

NS records show all servers that are authoritative for a zone, both primary and secondary servers for the zone specified in the SOA record, and primary name servers for any delegated zones.

Address (A) Records

The most basic entry in DNS, the A record maps the FQDN of a host to its IP address. When a client sends a standard forward lookup name-resolution query, the server uses A records to resolve the name.

Pointer (PTR) Records

The opposite of A records, PTR records provide reverse lookup services for DNS. That is, a PTR record maps an IP address to an FQDN. When a reverse lookup query is sent to a DNS server, such as through the NSLOOKUP utility, PTR records are consulted to resolve the address. PTR records are mapped in reverse lookup zones, which are in the in-addr.arpa zone.

Mail Exchanger (MX) Records

MX records designate a mail exchanging server for a DNS zone, which is a host that processes or forwards e-mail. In addition to the standard Owner, Class, and Type fields, MX records also support a fourth field: Mail Server Priority. This field is used when you have multiple mail servers in your domain, and mail exchangers with lower values are "preferred" over mail exchangers with higher values when determining which server to use to process an email message.

Service (SRV) Records

SRV records allow you to specify the location of servers providing a particular service, such as Web servers. You can create SRV records to identify hosts in the zone that provide a service, and then a resolver can find the A record of a service to resolve the name.

If you are having trouble with name-resolution services, where clients cannot successfully contact DCs, ensure that the appropriate SRV records exist for the DCs on the network.

Canonical Name (CNAME) Records

A CNAME record creates an alias for a specified host. This type of record is used most commonly to hide implementation details of your network. For example, say you have a Web server running at http://www.mycorp.com. The server that the Web site is running on might really be server1.mycorp.com. You don't want users to have to use the real server name, and you want the flexibility of being able to move the Web site to a newer, faster server in the future as traffic grows, without having to change the address of your Web site from server1.mycorp.com to server2.mycorp.com. CNAME provides the ability to alias the host name so that problems like this do not occur.


DDNS, defined in RFC 2136, is used in Windows 2000 in conjunction with DHCP. When a Windows 2000 client boots up and receives addressing information from DHCP, it can register itself with DNS, automatically adding the requisite resource records.

Dynamic Updates

DDNS is enabled/disabled through zone properties. To do so, open the DNS MMC console from the Start menu, right-click your forward or reverse lookup zone, and then click Properties. On the General property sheet is the Allow Dynamic Updates? option. The choices are Yes, No, and Only Secure Updates. When DDNS is enabled, DHCP manages the resource records for DHCP clients. When a DHCP lease expires, the DHCP service cleans up the A and PTR records from DNS. By default, a dynamic update is performed from Windows 2000 clients every 24 hours, or immediately when one of the following occurs:

  • A DHCP-obtained IP address is renewed or a new lease is obtained.

  • A static IP address is added or removed from a computer.

  • The TCP/IP configuration of a client changes.

  • A Plug and Play event occurs on a client, such as the installation of a new network adapter.

Secure Updates

In addition to enabling dynamic updates, you can configure Windows 2000 DNS to perform only secure updates. As just mentioned, this is enabled by selecting Only Secure Updates on the General property sheet of the desired zone. So what do secure updates do?

Once you have enabled secure updates, you can control which users and computers can register themselves into DNS. By default, all members of the Authenticated Users security group are granted permission, although this can be changed as necessary through access control lists (ACLs) by clicking the Security tab on a zone's property sheet.

A dynamic update in general requires that the client computers be capable of registering an FQDN. Windows 2000 clients are capable of this; Windows NT and 9X clients are not. As we've previously discussed, Windows 2000 DHCP can act as a proxy for these legacy clients, because DHCP can register them in DNS on their behalf. The reason the FQDN consideration is important is that once you've enabled secure updates, you can reserve FQDNs in DNS so that only certain users can use them. To do this, create a new host record in the DNS console with the desired FQDN. Then, on the Security tab, configure the ACL so that only the desired user can update the resource records associated with the particular FQDN.

Note that all resource records for a single FQDN share a single ACL. In other words, if you create an A record for workstation1.inside-corner.com and then create an MX record for the same host, there is only one ACL for the two records. This would be true even if you added additional records for the same host.

Pearson IT Certification Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Pearson IT Certification and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Pearson IT Certification products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.pearsonitcertification.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020