DNS Server Zone Transfer
Applies To: Windows Server 2008 R2
Domain Name System (DNS) enhances fault tolerance and load balancing by providing for server redundancy. For any given zone, a DNS server can act as a primary master server, which is the authority for a zone, or as a secondary server, which obtains its zone data from the zone's primary master server or another secondary server. This process is known as zone transfer.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-DNS-Server-Service |
The DNS server successfully completed transfer of version %1 of zone %2 to the DNS server at %3. | |
Microsoft-Windows-DNS-Server-Service |
The transfer of version %1 of zone %2 by the DNS server was aborted by the server at %3. To restart the transfer of the zone, you must initiate transfer at the secondary server. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server received a request from %1 for a UDP-based transfer of the entire zone. The request was ignored because full zone transfers must be made using TCP. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server received a zone transfer request from %1 for a non-existent or non-authoritative zone %2. | |
Microsoft-Windows-DNS-Server-Service |
A more recent version, version %1 of zone %2 was found at the DNS server at %3. Zone transfer is in progress. | |
Microsoft-Windows-DNS-Server-Service |
Zone %1 failed zone refresh check. Unable to connect to master DNS server at %2 to receive zone transfer. Check that the zone contains correct IP address for the master server or if network failure has occurred. For more information, see "To update the master server for a secondary zone" in the online Help. If available, you can specify more than one master server in the list for this zone. | |
Microsoft-Windows-DNS-Server-Service |
Invalid response from master DNS server at %2 during attempted zone transfer of zone %1. Check the DNS server at %2 and ensure that it is authoritative for this zone. This can be done by viewing or updating the list of authoritative servers for the zone. When using the DNS console, select zone %1 Properties at server %2 and click the Name Servers tab. If needed, you can add or update this server in the list there. As an alternative solution, you could also modify settings in the Zone Transfer tab to allow transfer of the zone to this and other DNS servers. | |
Microsoft-Windows-DNS-Server-Service |
A zone transfer request for the secondary zone %1 was refused by the master DNS server at %2. Check the zone at the master server %2 to verify that zone transfer is enabled to this server. To do so, use the DNS console, and select master server %2 as the applicable server, then in secondary zone %1 Properties, view the settings on the Zone Transfers tab. Based on the settings you choose, make any configuration adjustments there (or possibly in the Name Servers tab) so that a zone transfer can be made to this server. | |
Microsoft-Windows-DNS-Server-Service |
Failed transfer of zone %1 from DNS server at %2. The DNS server at %2 aborted or failed to complete transfer of the zone. Check the DNS server at %2 and ensure it is properly functioning and authoritative for zone %1. | |
Microsoft-Windows-DNS-Server-Service |
The master DNS server at %2 responded to IXFR (Incremental Zone Transfer) request for zone %1 with an invalid (FORMAT ERROR) response. DNS server performance and network bandwidth will both be improved by upgrading the DNS server at %2 to a run as either a Windows 2000 or later Microsoft DNS server or another IXFR-compatible DNS server implementation. | |
Microsoft-Windows-DNS-Server-Service |
Invalid IXFR (Incremental Zone Transfer) response from master DNS server at %2 during attempted incremental transfer of zone %1. Check the DNS server at %2, and verify its is running as a Windows 2000 or later Microsoft DNS server or another IXFR-compatible DNS server implementation. |