No results found

Your search did not match any results.

We suggest you try the following to help find what you're looking for:

 

  • - Check the spelling of your keyword search.
  • - Use synonyms for the keyword you typed, for example, try “application” instead of “software.”
  • - Try one of the popular searches shown below.
  • - Start a new search.

 

Trending Questions

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 Director. If advanced services are not disconnected from a zone, the zone will remain in Dyn Managed DNS. This guide helps you remove the Traffic Director 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

  • We recommend that upon acquiring an Oracle Cloud Infrastructure account, you begin replicating the Oracle Cloud Infrastructure traffic steering policy prior to removing the existing service from Managed DNS. However, in order to test the policy, you must use a zone that does not exist in your Managed DNS account. See Replicating Dyn Geolocation Services to a Geolocation Steering Traffic Management Policy in Oracle Cloud Infrastructure for more information.
  • When all Traffic Director functions are removed, answers will not be optimized.
  • In Oracle Cloud Infrastructure Traffic Management, there is currently no notification when a failover event has occurred.

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


Removing Traffic Director with A Records

By removing the service, you will temporarily be without the health monitoring, failover, round robin load balancing configurations, or geo steering functionality on your records until you successfully migrate the zone to Oracle Cloud Infrastructure and replicate the Traffic Director equivalent in Oracle Cloud Infrastructure DNS.

As the Traffic Director service encapsulates all records within the service itself, once removed all records within the service are removed as well. In order to prevent any DNS resolution failures, users must populate the desired A records outside the service directly on the hostname. By doing so, upon removing the Traffic Director service all DNS queries will be directed to the A records that were created directly on the hostname.

Populate Records on the Hostname

The Traffic Director service encapsulates all records within the service itself. When the service is removed, all records within the service are also removed. In order to prevent any DNS resolution failures, you will need to populate the desired A records outside the service directly on the hostname.


Dyn Traffic Director A Records

Remove the Traffic Director Service from Managed DNS

Important: By removing the service, you will temporarily be without the health monitoring, failover, round robin load balancing configurations, or geo steering functionality on their records until they successfully migrate the zone to Oracle Cloud Infrastructure and replicate the Traffic Director equivalent in Oracle Cloud Infrastructure DNS.

  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 Director service.
  4. Click the Services tab.
  5. Click Manage under Traffic Director for the node where you want to remove Traffic Director.
  6. In the Service Controls section, expand Attached Nodes to view currently attached zone nodes.
  7. Click the X for the node you want to remove. The node is immediately removed from the Traffic Director Service.

The following image shows an example of the DNS Records view after Traffic Director is removed. The A records that were in the service remain on the hostname.


Dyn Traffic Director A Records Service Removed

Migrate Zones

When all Traffic Director 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 tool. See Transfer from Dyn Managed DNS to Oracle Cloud Infrastructure DNS.

Replicate the Traffic Director Policies on 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

When the Traffic Steering policy is replicated on Oracle Cloud Infrastructure DNS and attached to the domain name, the A records that were populated outside the service will remain on the hostname. 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.

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


Dyn Traffic Director A Records Remain


Remove Traffic Director with CNAME Records

For customers who want to migrate a Dyn Traffic Director with CNAME records, please contact support to discuss available options based on your DNS implementation.