Start a zone transfer at a secondary server

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

This procedure checks to see if the start of authority (SOA) resource record in the secondary zone is the most recent version of the SOA resource record in the primary zone. If the SOA resource records are synchronized, there is no zone transfer. If the SOA resource records are not synchronized, there is a zone transfer.

By default, the Domain Name System (DNS) server only allows a zone transfer to authoritative DNS servers that are listed in the name server (NS) resource records for the zone.

You can perform this procedure by using the DNS snap-in or by using the Dnscmd command-line tool.

Administrative credentials

To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using the Run as command to perform this procedure.

Starting a zone transfer at a secondary server

• Using the Windows interface

• Using the command line

To start a zone transfer at a secondary server using the Windows interface

1. Open the DNS snap-in.

2. In the console tree, right-click the applicable zone, and then click Transfer from master.

To start a zone transfer at a secondary server using the command line

• At a command prompt, type the following command, and then press ENTER:

  dnscmd ServerName /ZoneRefresh ZoneName

  Value	Description
  ServerName	Required. Specifies the DNS host name of the DNS server. You can also type the Internet Protocol (IP) address of the DNS server. To specify the DNS server on the local computer, you can also type a period (.)
  /ZoneRefresh	Required. Updates the secondary zone.
  ZoneName	Required. Specifies the name of the secondary zone to update.