The Managing DNS Zones and Resource Records module provides you with the instruction and server hardware to develop your hands-on skills in the defined topics. This module includes the following exercises:
- Configuring AD Integration of Primary DNS Zones
- Creating DNS Zone Types
- Creating and Manage DNS Resource Records
Lab time: It will take approximately 1 hour to complete this lab.
The following exam objectives are covered in this lab:
- Creating DNS Primary Zones
- Managing AD Integrated Zones; creating DNS Secondary Zones, Stub Zones, and Reverse - - - Lookup Zones
- Creating different Resource Records
- Using nslookup to view Resource Records
Exercise 1 - Configuring AD Integrated Zones
Domain Name System (DNS) servers traditionally store zone information in a standard text file document, with a file name such as domainname.com.dns, in the local disk volume of the server. With Windows Server DNS, zone data can be stored in Active Directory and the registry if the server is configured to run as a domain controller. Active Directory (AD) Integrated zones provide security for hostname registration, and a single topology for replicating AD data and DNS zone information with other DNS servers that are running the domain controller role.
In this exercise, you will perform the tasks required to deploy and configure AD Integrated zones.
Exercise 2 - Creating DNS Zone Types
In addition to the Primary DNS zone and Active Directory Integrated zones that maintain writeable copies of DNS Resource Records, you can configure other types of zones (like Secondary and Stub zones) to ensure that name resolution traffic is distributed among servers in a corporate network.
Secondary DNS zones are read-only copies of the Resource Records that are collected from the Primary DNS. Changes to the Primary DNS zones are replicated to other Secondary zones in a process called Zone Transfer. A Zone Transfer can be initiated manually, and you can set the parameters for when Zone Transfer will occur from the Primary DNS zone to the Secondary DNS zone. DNS clients can resolve host names and IP addresses using a Secondary DNS zone as well.
Stub zones maintain a subset of read-only Resource Records from the Primary DNS server. This type of zone cannot resolve hostnames and IP addresses; however, Stub zones can redirect the DNS client to the authoritative DNS server that has authority for resolving hostnames for the given DNS zone.
Exercise 3 - Managing DNS Resource Records
DNS servers maintain Resource Records (RRs) most of which are registered dynamically by devices like domain controllers, member servers, and workstations in the Windows Active Directory Domain. These RRs are used by DNS to resolve a host name to its numeric IP address counterpart whenever requested by a DNS resolver (Windows client) or application. There are RRs that are statically entered, like Mail Exchanger, which identifies the server that receives e-mail from the Internet. Computers that do not support DNS dynamic updates must have their applicable RRs entered to allow other computers in the network to locate them.
See the full benefits of our immersive learning experience with interactive courses and guided career paths.