No results found

Your search did not match any results.

The Oracle Cloud Infrastructure zone migration tool only allows the direct transfer of DNS zones that do not have advanced services attached to them, such as Traffic Management. If advanced services are not disconnected from a zone, the zone will remain in Dyn Managed DNS. This guide helps you remove the Traffic Management service from your zones in Dyn Managed DNS so that you can use the Oracle Cloud Infrastructure zone migration tool to transfer DNS zones.

Important

The following information provides guidance on how to remove your service from Dyn and replicate the service in Oracle Cloud Infrastructure.


Removing Dyn Traffic Management with A Records

Removing the service will still keep the DNS A records on the hostname, preventing any interruptions to DNS resolution. However, you will temporarily be without the health monitoring, failover, round robin load balancing, or geo steering functionality on your records until you migrate the zone to Oracle Cloud Infrastructure and replicate the Traffic Management policy in Oracle Cloud Infrastructure. 

The DNS A records that were defined in the service will remain on the hostname Traffic Management was deployed on so there will not be any interruptions to the DNS resolution itself. However, geo steering or round robin load balancing configurations and answers will not be optimized once the service is removed from the hostname.

Remove the Traffic Management Service from Dyn Managed DNS

Important: You will temporarily be without the health monitoring, failover, round robin load balancing, or geo steering functionality on your records until you migrate the zone to Oracle Cloud Infrastructure and replicate the Traffic Management policy in Oracle Cloud Infrastructure.

  1. Log into your Dyn Managed DNS account.
  2. Click Overview or Manage DNS.
  3. Click Manage beside the zone where you want to remove the Traffic Management service.
  4. Click the Services tab.
  5. Click Manage under Traffic Management for the node where you want to remove Traffic Management.
  6. Click Delete Service.
  7. Click Delete to confirm your decision to delete the service.

The following image shows an example of the Address Pools view after Traffic Management is removed. The A records that were in the service remain on the hostname Traffic Management was deployed on. 

Dyn Traffic Management address pools view

The following image shows an example of the DNS Records view after Traffic Management is removed. The A records that were in the service remain on the hostname Traffic Management was deployed on. Please note that although removing the Traffic Management service will not interrupt DNS resolution, geo steering and health monitoring will be removed and will not function until the zone is migrated to Oracle Cloud Infrastructure and the equivalent service is attached to the hostname.

Dyn Traffic Management DNS Records view

Migrate Zones

After all Traffic Management Services (along with any other advanced features in use) are removed, leaving just the A records on the hostname, the zone is now in an eligible state to be migrated with the Dyn to Oracle Cloud Infrastructure migration tooling. See Transfer from Dyn Managed DNS to Oracle Cloud Infrastructure DNS.

Replicate the Traffic Management Service in Oracle Cloud Infrastructure

If you have not already replicated your traffic steering policy, you can replicate your steering policy when the zone has been migrated to Oracle Cloud Infrastructure. See Replicating Dyn Geolocation Services to a Geolocation Steering Traffic Management Policy in Oracle Cloud Infrastructure.

(Optional) Delete A Records from the Zone 

After the Traffic Management policy is replicated on Oracle Cloud Infrastructure and attached to the hostname, the old A records from the migration will remain on the hostname, as highlighted in the following image. You can delete these records from the zone. However, if you leave the records attached to the zone, it will have no impact on the traffic steering service handling DNS resolution. See Managing DNS Service Zones for information on how to delete a record.

The following image shows an example of how the A records that were populated outside the service remain on the hostname.

Oracle Cloud Infrastructure A records in DNS Zone Management


Removing Dyn Traffic Management with a CNAME Record

When you remove the service, health monitoring, global server load balancing, round robin load balancing, or failover functionality on the hostname is temporarily unavailable until you migrate the zone to Oracle Cloud Infrastructure and replicate the Traffic Management policy in Oracle Cloud Infrastructure.

Additionally, without a Traffic Management service deployed on a hostname, only a single CNAME can be deployed on the hostname itself. If you have CNAME record types in your Traffic Management service, you will need to delete all but one CNAME prior to removing the service itself. The CNAME that is selected to remain on the hostname will be answering all DNS queries until the zone is migrated and the service is replicated on Oracle Cloud Infrastructure.

Remove the Traffic Management Service from Dyn Managed DNS

Important: You will temporarily be without the health monitoring, global server load balancing, round robin load balancing, or failover functionality on the hostname until you migrate the zone to Oracle Cloud Infrastructure and replicate the Traffic Management policy in Oracle Cloud Infrastructure.

  1. Log into your Dyn Managed DNS account.
  2. Click Overview or Manage DNS.
  3. Click Manage beside the zone where you want to remove the Traffic Management service.
  4. Click the Services tab.
  5. Click Manage under Traffic Management for the node where you want to remove Traffic Management.
  6. Click Delete Service.
  7. Click Delete to confirm your decision to delete the service.

The following image shows an example of an updated Traffic Management service with a single CNAME. All DNS queries are being answered by the single CNAME. 


Dyn Traffic Management CNAME view

The following image shows an example of a Traffic Management service that has been removed leaving just the single CNAME record on the hostname.


Dyn Traffic Management with a single CNAME record on the hostname

Migrate Zones

Once all Traffic Management Services (along with any other advanced features in use) are removed, leaving just the CNAME record on the hostname, the zone is now in an eligible state to be migrated with the Dyn to Oracle Cloud Infrastructure migration tooling. See Transfer from Dyn Managed DNS to Oracle Cloud Infrastructure DNS.

Replicate the Traffic Management Service in Oracle Cloud Infrastructure

If you have not already replicated your traffic steering policy, you can replicate your steering policy when the zone has been migrated to Oracle Cloud Infrastructure. See Replicating Dyn Geolocation Services to a Geolocation Steering Traffic Management Policy in Oracle Cloud Infrastructure.

Create a New Hostname for the Traffic Management Service 

After the zone has been migrated to Oracle Cloud Infrastructure for the Traffic Management services that contained the CNAME record type, you need to create a new hostname for the Traffic Management service to be attached to Oracle Cloud Infrastructure DNS to avoid any DNS resolution interruptions.

In the example above, Dyn’s Traffic Management was attached to trafficmanagement.dns-migration.net. The user needs to create a new hostname for the service to be attached to. Any hostname label can be used. In the example below, trafficmanagement-1.dns-migration.net is used.


Oracle Cloud Infrastructure attached domains to the hostname

Test the New Traffic Management Policy

After the Oracle Cloud Infrastructure Traffic Management Steering policy is created and the newly created hostname is attached to the service, you can perform tests against the policy.

Update the CNAME on the Original Dyn Managed DNS Hostname

When the policy is ready for production, you will update the CNAME record on the original hostname in Dyn Managed DNS (which currently has the single CNAME you consolidated down to) to now reflect the new created hostname the Oracle Cloud Infrastructure Traffic Management Steering failover policy was attached to. In the above example it would be trafficmanagement-1.dns-migration.net.

The following image shows an example of the CNAME record in the Oracle Cloud Infrastructure DNS service before it is updated.


Oracle Cloud Infrastructure CNAME record before it is updated

The following image shows an example of the CNAME record in the Oracle Cloud Infrastructure DNS service after it is updated to the newly created hostname the Traffic Management failover policy is attached to.


Oracle Cloud Infrastructure CNAME record after it is updated