To replicate an Active Failover policy in Oracle Cloud Infrastructure Traffic Management, you will need to note your current Dyn Active Failover configurations and then create a new Traffic Management Failover Policy.
Locate Dyn Active Failover Configurations
- Log into your Dyn account.
- Click Overview or Manage DNS.
- Click Manage beside the zone where you want to view the Active Failover service.
- Click Services on the menu bar.
- Scroll to the Active Failover heading.
- Click Manage beside the Active Failover node you want to view.
The Active Failover service for the node appears.
- Note the following information to be used when creating a Failover policy in Oracle Cloud Infrastructure’s Traffic Management service:
- TTL – The Time to Live for responses from the steering policy.
- IP Address or FQDN – The primary IP address to be monitored.
- Failover Address – The secondary IP address. This is the IP address that will be used if the primary IP address is no longer responding to the protocol monitors.
- Health Monitoring
- Interval – The period of time between health checks of the IP host.
- HTTP/HTTPS Protocol – The network protocol used to interact with your endpoint.
- Port – The port for the monitor to look for a connection.
- Path – The specific path on the target to be monitored.
- Retries – The maximum time to wait for a reply before marking the health check as failed.
- Header – The request header name and value.
- Active failover subdomain and zone – The domain name you want to attach to the policy.
Create a Failover Traffic Management Policy in Oracle Cloud Infrastructure
To create a new Traffic Management Failover Policy in Oracle Cloud Infrastructure, see “To create a Failover policy” in Managing Traffic Management Steering Policies.
The following information is important to note:
- User Defined Timeouts – Dyn’s Managed DNS monitoring timeout value was set at 10 seconds. Oracle Cloud Infrastructure Health Checks allows users to choose a 10, 20, 30, or 60 second timeout. The recommended Health Check interval is 60 seconds. It is recommended that you set the timeout value lower than the health check interval.
- Path – HTTP/HTTPS protocols in Oracle Cloud Infrastructure Health Checks require a 200 response code in order to consider an endpoint as healthy.
- Expected Data – Oracle Cloud Infrastructure Health Checks does not currently support expected data.
Use the following table to identify equivalent information in Oracle Cloud Infrastructure. Dyn Active Failover includes some fields that are not available in the Traffic Management Steering service.