Configuring Internet access for DNS in WindowsServer2003

Profile
This step-by-step article describes how to configure Internet access for Domain Name System (DNS) in the Windows Server 2003 product. DNS is the core name resolution tool used on the Internet. DNS is responsible for parsing between host names and Internet addresses

How to start a stand-alone server running Windows Server 2003 from a stand-alone server running Windows Server 2003 to become a network's DNS server. The first step is to assign a static Internet Protocol (IP) address to the server. DNS servers should not use dynamically assigned IP addresses because dynamic changes to addresses can cause clients to lose contact with the DNS server.

1th Step: Configure TCP/IP
Click Start, point to Control Panel, point to Network Connection, and then click Local Area Connection.
Click Properties.
Click Internet Protocol (TCP/IP). , and then click Properties.
Click the General tab.
Click to use the following IP address, and then type the IP address, subnet mask, and default gateway address in the appropriate boxes.
Click Advanced, and then click the DNS tab.
Click Attach the primary and connection specific DNS suffix.
Click to select the Append parent suffix of the primary DNS suffix check box.
Click to select the Register this connection's address check box in DNS.

Note that a DNS server running Windows Server 2003 must designate its DNS server as itself. If the server needs to resolve the name from its Internet service provider (ISP), you must configure a forwarder. Forwarders are discussed in the section on how to configure forwarders later in this article.
Click OK three times.

Note: If you receive a warning from the DNS Cache resolver service, click OK to close the warning. The cache resolver is trying to contact the DNS server, but you have not completed the configuration of the server.

Step 2nd: Install the MICROSOFTDNS server
Click Start, point to Control Panel, and then click Add or Remove Programs.
Click Add or Remove Windows components.
In the list of components, click Network Services (but do not select or clear the check box), and then click Details.
Click to select the domain Name System (DNS) check box, and then click OK.
Click Next.
After you are prompted, insert the Windows Server 2003 CD-ROM into your computer's CD-ROM or DVD-ROM drive.
When the installation is complete, click Finish on the Completing the Windows Components Wizard page.
Click Close to close the Add or Remove Programs window.

Step 3rd: Configure the DNS server
To configure DNS using the DNS snap-in in Microsoft Management Console (MMC), follow these steps:
Click Start, point to Programs, point to Administrative Tools, and then click DNS.
Right-click the forward lookup zone, and then clicking New Area. When the New Zone Wizard starts, click Next.

You will then be prompted to select a zone type. Zone types include:

Primary zone: Creates a copy of the zone that can be updated directly on this server. This area information is stored in one. DNS text file.
Secondary zone: The standard secondary zone replicates all information from its primary DNS server. The primary DNS server can be an Active Directory zone, a primary zone, or a secondary zone that is configured for zone replication. Note that you cannot modify zone data on a secondary DNS server. All data is replicated from the primary DNS server.
Stub zone: The stub zone contains only the resource records that are required to identify the authoritative DNS servers for the zone. These resource records include the name server (NS), the starting authority (SOA), and the possible glue host (A) record. Active Directory also has an option to store the area. This option is available only when the DNS server is a domain controller.
The new forward lookup zone must be an integrated area of the primary or Active Directory so that it can accept dynamic updates. Click Main, and then click Next.
The new zone contains locator records for the domain based on Active Directory. The zone name must be the same as the name of the domain that is based on active Directory, or the logical DNS container for that name. For example, if the domain based on active Directory is named "support.microsoft.com", then a valid zone name can only be "support.microsoft.com".

Accept the default name for the new zone file. Click Next.

Note: Experienced DNS administrators may want to create reverse lookup zones, so they are advised to delve into this branch of the wizard. The DNS server can parse two basic requests: forward search requests and reverse search requests. Forward search is more common. A forward search resolves a host name to an IP address with a "A" or a host resource record. The reverse lookup resolves the IP address to a host name with a PTR or pointer resource record. If you configure a reverse DNS zone, you can create an associated reverse record automatically when you create the original forward record.

How to remove the root DNS zone
A DNS server running Windows Server 2003 follows a specific step in its name resolution process. The DNS server first queries its cache, then checks its zone records, sends the request to the forwarder, and finally attempts to resolve using the root server.

By default, the MicrosoftDNS server is connected to the Internet to further process DNS requests with root hints. When using the Dcpromo tool to promote a server to a domain controller, the domain controller requires DNS. If you install DNS during the promotion process, a root zone is created. This root zone indicates to your DNS server that it is a root internet server. Therefore, your DNS server does not use forwarders or root hints during name resolution.
Click Start, point to Administrative Tools, and then click DNS.
Expand ServerName, where ServerName is the name of the server, click Properties, and then expand the Forward lookup zone.
Right-click the "." Area, then delete.

How to configure Forwarders
Windows Server 2003 can take full advantage of DNS forwarders. This feature forwards DNS requests to an external server. If the DNS server cannot find a resource record in its zone, the request can be sent to another DNS server for further attempts to resolve. A common scenario is a forwarder configured to your ISP's DNS server.

Click Start, point to Administrative Tools, and then click DNS.
Right-click ServerName, where ServerName is the name of the server, and then clicking the Forwarders tab.
Click a DNS domain in the DNS domain list. Or, click New, type the name of the DNS domain for which you want to forward the query in the DNS domain box, and then click OK.
In the Forwarder IP address box for the selected domain, type the IP address of the first DNS server that you want to forward to, and then click Add.
Repeat step 4 to add the DNS server that you want to forward to.
Click OK.

How to configure root hints
Windows can use root hints. Root hints resource records can be stored in Active Directory or text files (%systemroot%\system32\dns\cache.dns). Windows uses a standard InterNIC root server. In addition, when a server running Windows Server 2003 queries the root server, it will use the latest root service
The list of services updates itself. Click Start, point to Administrative Tools, and then click DNS.
Right-click ServerName, where ServerName is the name of the server, and then clicking Properties.
Click the Root Hints tab. The DNS server's root server is listed in the list of name servers.

How to configure DNS proxy and network address translation (NAT) devices after a firewall can restrict access to ports. DNS uses UDP port A and TCP port 53. The DNS service Management console also uses RCP. RCP uses port 135. These problems can occur when you configure DNS and firewalls.