سوال: تنظيم دو dns در يك شبكه [بایگانی]

zman123456

دوشنبه 24 آبان 1389, 13:35 عصر

خودم يه چيزي پيدا كردم البته بقيه نظر بدن.

HOW TO Configure a Secondary Name Server in Windows Server 2003
This step-by-step article describes how to configure a secondary DNS server.
Identify the Secondary Name Server

On the primary DNS server, identify an additional name server. To do this, follow these steps:

Click Start, point to Administrative Tools, and then click DNS.
In the console tree, expand Host name (where Host name is the host name of the DNS server).
In the console tree, expand Forward Lookup Zones.
Right-click the zone that you want (for example, example.com), and then click Properties.
Click the Name Servers tab, and then click Add.
In the Server fully qualified domain name (FQDN) box, type the host name of the server that you want to add.

For example, type namesvr2.example.com.
In the IP address box, type the IP address of the name server that you want to add (for example, 192.168.0.22), and then click Add.
Click OK, and then click OK.
In the console tree, click Reverse Lookup Zones, right-click the zone that you want, and then click Properties.
Click the Name Servers tab, and then click Add.
In the Server name box, type the host name of the server that you want to add.

For example, namesvr2.example.com.
In the IP address box, type the IP address of the name server that you want to add (for example, 192.168.0.22), and then click Add.
Click OK two times.

Install DNS on the Secondary Name Server

To install the DNS service, follow these steps:

Log on to the computer as an administrator.
Click Start, point to Control Panel, and then click Add or Remove Programs.
Click Add\Remove Windows Components.
In the Components list, click Networking Services (do not click to select or click to clear the check box), and then click Details.
Click to select the Domain Name System (DNS) check box, and then click OK.
On the Windows Components page, click Next.
Insert the Windows 2003 Server CD when you are prompted, and then click OK.
On the Completing the Windows Components Wizard page, click Finish.
Click Close.

DNS is now installed. To start the DNS snap-in, click Start, point to Administrative Tools, and then click DNS.

Configure the Forward Lookup Zone

To configure the forward lookup zone on the secondary name server, follow these steps:

Log on to the secondary name server as an administrator.
Click Start, point to Administrative Tools, and then click DNS.
In the console tree, under DNS, click Host name (where Host name is the host name of the DNS server).
In the console tree, click Forward Lookup Zones.
Right-click Forward Lookup Zones, and then click New Zone.
When the New Zone Wizard starts, click Next to continue.
Click Secondary Zone, and then click Next.
In the Name box, type the name of the zone (for example, example.com), and then click Next.
On the Master DNS Servers page, type the IP address of the primary name server for this zone, click Add, click Next, and then click Finish.

Configure the Reverse Lookup Zone

To configure the reverse lookup zone on the secondary name server, follow these steps:

Click Start, point to Administrative Tools, and then click DNS.
In the console tree, click Host name (where Host name is the host name of the DNS server).
In the console tree, click Reverse Lookup Zones.
Right-click Reverse Lookup Zones, and then click New Zone.
When the New Zone Wizard starts, click Next to continue.
Click Secondary zone, and then click Next.
In the Network ID box, type the network ID (for example, type 192.168.0), and then click Next.

Note The network ID is that portion of the TCP/IP address that pertains to the network.

For additional information about TCP/IP networks, click the article number below to view the article in the Microsoft Knowledge Base:

164015 (http://support.microsoft.com/kb/164015/EN-US/) (http://support.microsoft.com/kb/164015/EN-US/ ) Understanding TCP/IP Addressing and Subnetting Basics

On the Zone File page, click Next, and then click Finish.

Troubleshoot

The Zone Is Not Loaded by the DNS Server

· When you select a zone on the secondary name server, you may recieve the following error message in the right pane of the DNS window:
Zone not loaded by DNS Server

The DNS server encountered an error while attempting to load the zone.
The transfer of zone data from the master server failed.
This issue may occur if zone transfers are disabled. To resolve this issue, follow these steps:

Log on to the primary name server computer as an administrator.
Click Start, point to Administrative Tools, and then click DNS.
In the console tree, click Host name (where Host name is the host name of the DNS server).
In the console tree, click Forward Lookup Zones.
Under Forward Lookup Zones, right-click the zone that you want (for example, example.com), and then click Properties.
Click the Zone Transfers tab.
Click to select the Allow zone transfers check box, and then click one of the following options:

To any server
Only to servers listed on the Name Servers tab
Only to the following servers.

Note If you click Only to the following servers, type the IP address of the secondary name server in the IP address box, and then click Add.

Click Apply, and then click OK.
Quit the DNS snap-in.

· How to Troubleshoot DNS

To troubleshoot and obtain information about the DNS configuration, use the Nslookup.exe utility.

For additional information about using Nslookup, click the article number below to view the article in the Microsoft Knowledge Base:
200525 (http://support.microsoft.com/kb/200525/EN-US/) (http://support.microsoft.com/kb/200525/EN-US/ ) Using Nslookup.exe

منبع: http://support.microsoft.com/kb/816518

يكي ديگه:

Adding a Secondary DNS Server
Updated: March 2, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Domain Name System (DNS) design specifications recommend that at least two DNS servers be used to host each zone. For standard, primary zones, a secondary server is required to add and configure the zone so that it appears to other DNS servers in the network. For directory-integrated, primary zones, secondary servers are supported but not required for this purpose. For example, two DNS servers running on domain controllers can be redundant primary servers for a zone. They can provide the same benefits as adding a secondary server while also providing additional benefits.
Secondary servers can be used to offload DNS query traffic in areas of the network where a zone is heavily queried. In addition, if a primary server is unavailable, a secondary server can provide some name resolution in the zone until the primary server is available.
If you add a secondary server, try to locate it as close as possible to clients that have a high demand for names that are used in the zone. Also, consider placing secondary servers across a router, either on other subnets (if you use a routed local area network (LAN)) or across wide area network (WAN) links. This constitutes a good use of a secondary server as a local backup in scenarios in which an intermediate network link becomes the point of failure between DNS servers and clients that use the zone.
Because a primary server always maintains the master copy of updates and changes to the zone, a secondary server relies on DNS zone transfer mechanisms to obtain its information and keep the information current. Issues such as zone transfer methods — using either full or incremental zone transfers — are more applicable when you use secondary servers.
When you consider the impact of zone transfers that are caused by secondary servers, consider their advantage as a backup source of information, and measure this against the added cost that they impose on your network infrastructure. A simple rule is that for each secondary server that you add, network usage (because of added zone replication traffic) increases, and so does the time that is required to synchronize the zone at all secondary servers.
Secondary servers are used most heavily for forward lookup zones. If you are using reverse lookup zones, it is not necessary to add as many secondary servers for those zones. Typically, a secondary server for a reverse lookup zone is not used outside the network and subnet that correspond to the reverse zone.
To complete this task, perform the following procedure:
Add a secondary server to a zone (http://technet.microsoft.com/en-us/library/cc779571%28WS.10%29.aspx)