In this exercise you will perform the tasks required to create and manage DNS zones. Please refer to your course material or Microsoft Technet to gain an understanding of DNS zones.

Please note that you will need to have completed exercise 1 to continue with this exercise. If you have not done so already, please ensure you have installed the DNS role as explained in exercise 1.

Step 1

From Domain Server open the DNS Manger Snap-in from Administrative tools or type in dnsmgmt.msc from the run or search all programs and files utilities.

Step 2

There are a number of ways to configure DNS zones; configuration can be carried out using the DNS Server Wizards which can be accessed by right clicking the DNS Server in the DNS management console and selecting either the Configure DNS Server or New Zone menu items. In this example, select New Zone .

The following images reflect a standard forward lookup zone:

Create a primary zone :

Select Forward lookup zone :

Select your zone name:

Choose the filename that you wish the entries to be stored in:

Allow both secure and non-secure updates:

Finally finish creating the zone:

The zone as its created in DNS snap in:

Step 3

Create the following zones types in the DNS Manger console using the new zone wizard. You can choose your own zone names or use the example names given (the previous walkthrough shows example 1):

Forward lookup zone

• Primary Zone
• Labs.com
• Non secure and Secure Updates

Active Directory Integrated zone

For this zone, you will need to connect to the Domain Controllerand not the domain server.

• Connect to AD Server
• Primary Zone
• Secure only
• Store in Active Directory
• ABCompany.com

Stub zone

• Connect to Domain Server
• PartnerCompany.com
• Do not store in Active Directory
• Master DNS Severs 192.168.0.2

Reverse lookup zone

• Primary Zone
• Store in Active Directory
• To all DNS servers in the domain
• IPV4
• 192.168.0

Step 4

Open Domain Controller and change the settings on the Active Directory integrated zone you created in the last step to reflect the following parameters:

• Dynamic updates Nonsecure and secure
• Ageing 10 Days
• TTL 3 Hours

Step 5

Once you have created the above zones try creating different record types in each zone for example:

• A Record (www.ABCompany.com)
• MX Record (mailhost.ABCompany.com)
• CNAME records (www.companyname.com resolve to www.ABCompany.com)

For additional information on DNS record types please refer to your course material or Microsoft Technet

Summary

In this exercise you created a number of different zone types; these zones are dependent on the type of DNS architecture of an organisation. You also configured some of the zone settings such as Dynamic updates and record TTL settings. Finally you created different DNS records; these records define the IP address of the device hosting a particular service.

Also try

• Create secondary zone off a primary zone.
• Change the configuration of SOA parameters to force a zone transfer.
• Enable scavenging on a zone to delete stale records.
• Create PTR records in the reverse lookup zone.

In this exercise you will perform the tasks required configure the DNS server settings. Please refer to your course material or Microsoft Technet to gain an understanding of managing DNS server settings.

Step 1

From Domain Controller open the DNS Manger Snap-in from Administrative tools or type in dnsmgmt.msc from the Run box or search all programs and files utilities.

Step 2

In order to configure the server settings right click the DNS Server in the console and select Properties

Step 3

Add a forwarder to the configuration with the following parameters: 8.8.8.8

Step 4

Delete the following entry from the Root hints configuration: k.root-servers.net.

Step 5

Enable Debug Logging and specify the following path for the log file C:\dnslog.txt

Step 6

Disable Recursion and Round Robin from the Advanced menu

Summary

In this exercise you configured a number of different DNS server properties. These properties configure how the DNS server operates overall and is not dependent zone configuration. If these settings are incorrectly implemented it can have a severe impact on name resolution as well as Active Directory functionality.

Also try

• Create conditional forwarder
• Troubleshoot event logging
• Investigate and configure Trust Anchors