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 Active Failover. If advanced services are not disconnected from a zone, the zone will remain in Dyn Managed DNS. This guide helps you remove the Active Failover 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 Active Failover service using the OCI traffic steering policies prior to removing the existing service from Managed DNS. See Replicating an Active Failover Policy in Oracle Cloud Infrastructure’s Traffic Management Service for more information. However, in order to test the policy you must use a zone that does not exist in their Managed DNS account.
  • 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 Active Failover with A Records

Removing the service will keep the primary record deployed on the hostname, preventing any interruptions to DNS resolution. However, users will temporarily be without the health monitoring and failover on their primary record until they successfully migrate the zone to Oracle Cloud Infrastructure and rebuild the Active Failover equivalent in Oracle Cloud Infrastructure DNS.


Remove the Active Failover Service from Managed DNS

Important: You will temporarily be without the health monitoring and failover on your primary record until they successfully migrate the zone to Oracle Cloud Infrastructure and replicate the Active Failover 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 Active Failover service.
  4. Click the Services tab.
  5. Click Manage in the far right column for the Active Failover node you want to remove.
  6. Click Delete Service.
  7. Click Delete to confirm your decision to delete the service.

When the Active Failover Service is deleted, the DNS record that was defined as the primary record will remain on the hostname where Active Failover was deployed.

The following example shows the primary A record attached to the hostname.


Dyn Active Failover Primary Record

When the Active Failover Service is deleted, the record that was defined as the primary record will remain on the hostname where Active Failover was deployed.


Dyn Active Failover Primary Record Remains


Migrate Zones

When all Active Failover Services are removed, only the primary records remain on the hostname and the zone is now in an eligible state to be migrated. See Transfer from Dyn Managed DNS to Oracle Cloud Infrastructure DNS.


Replicate the Active Failover Service on Oracle Cloud Infrastructure

If you have not already replicated your active failover policy, you can replicate your failover policy when the zone has been migrated to Oracle Cloud Infrastructure. See Replicating an Active Failover Policy in Oracle Cloud Infrastructure’s Traffic Management Service.


Removing Active Failover with CNAME

Removing the service will still keep the primary record deployed on the hostname, preventing any interruptions to DNS resolution. However, users will temporarily be without the health monitoring and failover on their primary record until they successfully migrate the zone to Oracle Cloud Infrastructure and replicate the Active Failover equivalent in Oracle Cloud Infrastructure DNS.


Remove the Active Failover Service from Managed DNS

Important: You will temporarily be without the health monitoring and failover on your primary record until they successfully migrate the zone to Oracle Cloud Infrastructure and replicate the Active Failover 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 Active Failover service.
  4. Click the Services tab.
  5. Click Manage in the far right column for the Active Failover node you want to remove.
  6. Click Delete Service.
  7. Click Delete to confirm your decision to delete the service.

When the Active Failover Service is deleted, the DNS record that was defined as the primary record will remain on the hostname where Active Failover was deployed.

The following example shows the primary record, primary.cname.dns-migration.net.


Dyn Active Failover Primary Record

When the Dyn Active Failover service is removed, primary.cname.dns-migration.net remains attached to the service on the hostname.


Dyn Active Failover Service Removed and Primary Record Remains on Host


Migrate Zones

When all Active Failover Services are removed, along with any other advanced features, only the primary record remains on the hostname and the zone is now in an eligible state to be migrated. See Transfer from Dyn Managed DNS to Oracle Cloud Infrastructure DNS.


Replicate the Active Failover Service on Oracle Cloud Infrastructure

If you have not already replicated your active failover policy, you can replicate your failover policy when the zone has been migrated to Oracle Cloud Infrastructure. See Replicating an Active Failover Policy in Oracle Cloud Infrastructure’s Traffic Management Service.

Important: Please review the following steps prior to replicating the service.

When the zone is migrated into Oracle Cloud Infrastructure DNS, for Active Failover services that contain the CNAME record type, you must follow an alternate process to leverage the Oracle Cloud Infrastructure failover service on the same hostname to avoid any DNS resolution interruptions.


Create a New Hostname for the Active Failover Service

Create a new hostname for the Failover service to be attached in Oracle Cloud Infrastructure DNS. In the above example, the Dyn Active Failover service was attached to active-failover.dns-migration.net, so you will create a new hostname for the service to be attached to activefailover-1.dns-migration.net.


Dyn Active Failover Create New Hostname


Test the Traffic Management Failover Policy

When the Oracle Cloud Infrastructure Traffic Management Failover policy is created and the new hostname is attached to the service, you can perform any desired testing against the policy.


Update the CNAME on the Original Dyn Managed DNS Hostname

When the policy is ready for production, you will modify the CNAME on the original hostname you were using in Dyn Managed DNS (which currently has the CNAME of the primary record of the active Failover service) to reflect the new hostname the Oracle Cloud Infrastructure Failover service was attached to. In the above scenario, activefailover.dns-migration.net will CNAME to activefailover-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.


Dyn Active Failover CNAME Before

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.


Dyn Active Failover CNAME After