The following questions may be useful in the event that your zone transfer was not successful.
1. Have you configured your master server to allow zone transfers from our servers?
Click for More Info
All zone data is transferred through our Provisioning server provision1.dynect.net for primary zones, and xfrin1.dynect.net for secondary zones. Check your nameserver’s logs to see if it is rejecting transfers from our servers, as this is a sure sign of a problem. Click here for more information on allowing zone transfers.
DynECT Provisioning Servers
| Server |
Use For This Zone Type |
IP Address |
| provision1.dynect.net |
Primary Zones – IPv4 Address |
208.78.68.67 |
|
Primary Zones – Alternate Server |
204.13.249.67 |
|
Primary Zones – IPv6 Address |
2600:2001:0:1::67 |
|
Primary Zones – IPv6 Alternate Address |
2600:2003:0:1::67 |
| xfrin1.dynect.net |
Secondary Zones – IPv4 Address |
208.78.68.65 |
|
Secondary Zones – Alternate Server |
204.13.249.65 |
|
Secondary Zones – IPv6 Address |
2600:2001:0:1::65 |
|
Secondary Zones – IPv6 Alternate Address |
2600:2003:0:1::65 |
Note: Make sure that you enter the Primary IP address as the first server to send notifies to and receive transfer requests from. The Alternate address as an offline secondary source.
Note: Dyn’s Managed DNS supports zone transfers via AXFR(full) or IXFR(incremental) zone transfers. Please see your current DNS provider’s documentation for whether they support these protocols.
2. Is your firewall allowing TCP and UDP port 53 through to your server?
Click for More Info
Our server must be able to contact your server on port 53, both TCP and UDP, to be able to transfer your zone.
3. Is your zone file in BIND or tinyDNS format?
Click for More Info
Zone files from some providers are not in a format recognized correctly by Dyn’s Managed DNS. Some of these issue can be corrected by the use of a Dyn provided script at github.com found here: Zonefile_Repair.
4. How can I transfer my DNSSEC-signed zone?
Click for More Info
Please review all zones for correctness after uploading them to Managed DNS.
Issues While Transferring Your DNS to Dyn
1. Have you published your zone? Once the zone successfully transfers, the zone must be published to Dyn’s nameservers before we can respond to DNS queries. Click here for more information on publishing your zone.
2. Have you properly delegated your zone to Dyn’s nameservers? Delegation is how the world finds the nameservers for your zone. Be sure that you have listed the correct nameservers with the correct IP addresses. Click here for more information on zone delegation.
3. Have you waited for the cached zone data on your recursive DNS servers to expire? It can take several hours for some recursive DNS servers to clear cached data. Extremely long TTL values can lead to even longer delays.
« DNS Knowledge Base
