For Active Directory–integrated zones, it is also possible that the affected records for the query have been updated in Active Directory but not replicated to all DNS servers that are loading the zone.
By default, all DNS servers that load zones from Active Directory poll Active Directory at a set interval — typically, every 15 minutes — and update the zone for any incremental changes to the zone.
For more information about configuring the subnet prioritization feature, see "Configuring Subnet Prioritization" earlier in this chapter.
If a zone transfer from a Windows 2000 server to a third-party DNS server fails, check whether the zone includes any WINS or WINS-R records.
This method uses compression and includes multiple resource records in each message, substantially increasing the speed of zone transfers. However, BIND 4.9.4 and earlier does not support fast zone transfer.
This is unlikely to be a problem, because when the Windows 2000 DNS Server service is installed, fast zone transfer is disabled by default.
This section lists several common DNS problems and explains how to solve them.
If you see event ID 7062 in the event log, the DNS server has sent a packet to itself. Check the following: By default, the Windows 2000 DNS server always uses a fast method of zone transfer.
However, it prevents the resolver from using the round robin feature as defined in RFC 1794.
By using the round robin feature, the server rotates the order of A resource record data returned in a query answer in which multiple resource records of the same type exist for a queried DNS domain name.
The resolver cannot locate the PTR resource record for the name server that it is configured to use.