Примеры использования Zone transfers на Английском языке и их переводы на Русский язык
{-}
-
Official
-
Colloquial
Restrict zone transfers.
Zone transfers take place between primary and secondary DNS servers.
All DNS servers permit zone transfers to any server.
To allow zone transfers, select the Allow zone transfers check box.
This prevents these records from being replicated to these other servers during zone transfers.
Permits zone transfers to any DNS server.
By default, servers running Windows Server 2008(and later version BIND servers) use a faster,compressed format during zone transfers.
If you allowed zone transfers, do one of the following.
This is a secure configuration, but for increased security,this setting should be changed to the option that allows zone transfers to specified IP addresses.
To allow zone transfers to any server, click To any server.
Changing a zone from a secondary zone to a primary zone can affect other zone activities,including management of dynamic updates and zone transfers, and the use of DNS notify lists to notify other servers about changes in the zone. .
To disable zone transfers, clear the Allow zone transfers check box.
The DNS Server service supports incremental zone transfers between servers that replicate a standard zone. .
Permits zone transfers only to DNS servers that are specified by SecondaryIPAddress.
All DNS servers limit zone transfers to specified IP addresses.
Permits zone transfers only to DNS servers that are listed in the zone using name server(NS) resource records.
DNS servers that store DNS data in files use zone transfers to replicate information about a portion of the DNS namespace.
To allow zone transfers only to specific DNS servers, click Only to the following servers, and then add the IP address of one or more DNS servers.
To improve the security of your DNS infrastructure,allow zone transfers only for either the DNS servers in the name server NS resource records for a zone or for specified DNS servers.
To allow zone transfers only to the DNS servers that are listed on the Name Servers tab, click Only to servers listed on the Name Servers tab.
After you complete the zone transfers, convert the secondary zones to primary zones for the zones that were migrated.
Clients schedule zone transfers initially, when their databases are empty, and thereafter at regular intervals, in a pattern controlled by the values in the"refresh","retry", and"expire" fields in the SOA resource record of the zone apex.
All DNS servers limit zone transfers to servers that are listed in the name server(NS) resource records in their zones. .
If this zone will be used in performing zone transfers to BIND servers, this is a critical option because Berkeley Internet Name Domain(BIND) will not recognize WINS records.
After completing the zone transfers, convert any of the secondary zones to primary zones for the zones that were obtained from primary zones at the BIND servers.
So that additional servers can host a zone, zone transfers are required for replication and synchronization of all copies of the zone that are used at each server that is configured to host the zone.
To prevent these records from being used or included in zone transfers to BIND-based servers and other servers that do not recognize them, select the Do not replicate this record option when you configure WINS properties at the applicable zone. .
Although the DNS Server service supports incremental zone transfers and DNS clients and servers can cache recently used names, traffic considerations are sometimes still an issue, particularly when Dynamic Host Configuration Protocol(DHCP) leases are shortened and, as a result, dynamic updates in DNS are performed more frequently.
To modify zone transfer settings using the Windows interface.
Modifying zone transfer settings.