Configuring a secondary DNS server for Windows Server 2003 domain controllers

Environment:

The primary Dns:win 2003 domain Master Controller zone is automatically generated by the system (abbreviation a)

Host to be installed as secondary DNS: Win 2003 is not joined to the domain (abbreviation b)

Area: region.com

Action method:

1. Open the dns--> of a to expand the server name--> the right "forward search zone" selection attribute.

2. Point "Zone Copy" tab, check "Allow zone Copy", and add B's IP in "allow only to the following servers".

3. Click on the bottom right "notice", also add b IP.

This is the end of the operation on Machine A.

4. Install DNS on B, install the method slightly.

5. Open DNS for B, right-click server name "Configure Server".

6. "Create forward lookup zone"-->isp maintain the zone, a read-only copy resides on this server "--> input" region.com--> add a ip--> configure forwarding as needed--> complete.

A DNS event for B will receive an error message at this time.

Event Type: Warning

Event Source: DNS

Event Type: None

Event id:414

Date: 2005-1-24

Event: 13:53:42

Users: N/A

Computer: * *

Describe:

The DNS server currently does not have a domain name. Its DNS name is called a single label hostname, and there are no domains (such as "host" instead of "host.microsoft.com").

You may have forgotten to configure the primary DNS domain for the server computer. For more information, see the DNS Server log reference or configure the primary DNS suffix for client computers in the online Help.

When a DNS server has only a single label name, all domains created have default records (SOA and NS) that use this single label name as the server host name. When clients and other DNS servers use these records to find this server by name, they cause the lookup to be incorrect and fail.