Windows Server 2003 : Installing and Configuring DNS Servers (part 4)

Practice: Installing and Configuring a DNS Server

In this practice, you install and configure a DNS server on Server02, configure a primary zone, and test the DNS server.

Exercise 1: Installing the DNS Windows Component

To complete this exercise, you must have the Windows Server 2003 installation CD-ROM loaded in Server02.

1.	Log on to Server02.
2.	Open a command prompt and ping server01.contoso.com, and then ping server02.contoso.com. These two ping tests should succeed.
3.	Open Control Panel, and then click Add Or Remove Programs. The Add Or Remove Programs window opens.
4.	Click Add/Remove Windows Components. The Windows Components page of the Windows Components Wizard opens.
5.	In the Components area, highlight the Networking Services component. Be sure not to select the Networking Services check box.
6.	Click Details. The Networking Services window opens.
7.	In the Subcomponents Of Networking Services area, select the Domain Name System (DNS) check box.
8.	Click OK. In the Windows Components Wizard, the Networking Services check box should now be unavailable.
9.	Click Next. The Configuring Components page appears while the new component is being installed. After installation is complete, the Completing The Windows Components Wizard page appears.
10.	Click Finish.
11.	Click Close to close the Add Or Remove Programs window.
12.	Open Network Connections in Control Panel, and open the properties windows for your network connection.
13.	In the This Connection Uses The Following Items area, select Internet Protocol (TCP/IP) and click the Properties button.
14.	Set the Preferred DNS Server address to Server02’s IP address, 192.168.0.2. This ensures that Server02 is a client to the DNS service running on Server02.
15.	Click OK, and close the network connection properties window.
16.	In the command prompt window, type the command ipconfig /flushdns. This command resets the computer’s cache of host name resolutions.

Exercise 2: Configuring Forwarding

1.	Log on to Server02.
2.	Open the DNS console.
3.	Right-click Server02 in the console tree and select Properties.
4.	Click the Forwarders tab.
5.	Highlight All Other DNS Domains.
6.	In the Selected Domain’s Forwarder IP Address List box, type 192.168.0.1.
7.	Click Add.
8.	Click OK.
10.	In the DNS console, select the View menu and choose Advanced.
11.	Expand the Cached Lookups node.
12.	Drill down to find the cached resource record or records for contoso.com.

Exercise 3: Configuring a Primary Zone

1.	Log on to Server02.
2.	Open the DNS console.
3.	Right-click Server02 in the console tree, and select Configure A DNS Server from the shortcut menu. The Configure A DNS Server Wizard launches.
4.	Click Next. The Select Configuration Action page appears.
5.	Select the Create Forward And Reverse Lookup Zones option, and then click Next. The Forward Lookup Zone page appears.
6.	Click Next to accept the default selection, Yes, Create A Forward Lookup Zone Now. The Zone Type page appears.
7.	Click Next to accept the default selection, Primary Zone. The Zone Name page appears.
8.	In the Zone Name text box, type nwtraders.com, and then click Next. The Zone File page appears.
9.	Click Next to accept the default selection, Create A New File With This File Name. The Dynamic Update page appears.
10.	Click Next to accept the default selection, Do Not Allow Dynamic Updates. The Reverse Lookup Zone page appears.
11.	Click Next to accept the default selection, Yes, Create A Reverse Lookup Zone Now. The Zone Type page appears.
12.	Click Next to accept the default selection, Primary Zone. The Reverse Lookup Zone page appears.
13.	In the Network ID text box, type 192.168.0. The reverse lookup zone name is automatically configured in the Reverse Lookup Zone Name text box.
14.	Click Next. The Zone File page appears.
15.	Click Next to accept the default selection, Create A New File With This File Name. The Dynamic Update page appears.
16.	Click Next to accept the default selection, Do Not Allow Dynamic Updates. The Forwarders page appears.
17.	Click Yes, It Should Forward Queries To DNS Servers With The Following IP Addresses, and type Server01’s address, 192.168.0.1. Then click Next. If Server01 does not have Internet connectivity, the Searching For Root Hints dialog box will be visible for some time and, after the last step in this exercise, you will receive an error regarding Root Hints. The Completing The Configure A DNS Server Wizard page appears.
18.	Click Finish.
19.	In the DNS console, expand the console tree in the left pane so that you can see the new zone nwtraders.com listed in the Forward Lookup Zones folder. You can also see the new zone 192.168.0.x Subnet listed in the Reverse Lookup Zones folder. (If the DNS console is displayed in Advanced view, the zone will appear as 0.168.192.in-addr.arpa.)

Exercise 4: Testing the DNS Server

Windows Server 2003 allows you to verify your DNS server configuration with two tests locally on the DNS server computer. These two tests are included on the Monitoring tab of the server properties dialog box, available through the DNS console.

1.	While you are logged on to Server02 as Administrator, make sure you are connected to the Internet.
2.	In the console tree within the DNS console, right-click Server02 and select Properties. The SERVER02 Properties dialog box opens.
3.	Click the Monitoring tab.
4.	Select the A Simple Query Against This DNS Server check box and the A Recursive Query To Other DNS Servers check box.
5.	Click Test Now. The Test Results area shows the successful results of the tests you have just performed. If Server01 does not have Internet connectivity, the Recursive Query test will fail.
6.	Click OK to close the Server02 Properties dialog box.

Tip

You need to understand the DNS server tests for the exam. First, know that the simple test is based on a reverse lookup of the loopback address 127.0.0.1. Therefore, if the simple test fails, you should verify that a record named 1 is found in the reverse lookup zone named 0.0.127.in-addr.arpa (visible only in the DNS console Advanced view). Next, the recursive test verifies that the DNS server can communicate with other DNS servers and that the root hints are correctly configured.