To transition to an Oracle Cloud Infrastructure Traffic Management, you will need to note your current Dyn Traffic Director load balancing configurations. Use the instructions below to locate this configuration information.
We recommend that upon acquiring an Oracle Cloud Infrastructure account, you begin replicating the Dyn Traffic Director service using the OCI traffic steering policies 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.
Locate Load Balancing Configurations in Dyn Traffic Director
- Log into your Dyn account.
- Click Overview or Manage DNS.
- Click Manage beside the zone where you want to view the Traffic Director service.
- Click Services on the menu bar.
- Click Manage in the Actions column for the Traffic Director node you want to view.
- In the Service Controls section, note the following information:
- Label – The service name.
- TTL – The Time to Live for responses from the steering policy.
- Attached nodes – The attached domain names.
- In the Response Pools section, note the following information:
- Serve Count – The number of IPs served per DNS request from the list of available IPs.
- Label – The record name.
- Record Type – The record type that will be provided as the answer.
- For A records, note the Address.
- For CNAME records, note the Hostname.
- Weight – The number used to determine how often an answer is served in relation to other answers.
- Record Serve Mode – Indicates the behavior of each host if a Health Performance Check shows that an IP address is down.
- In the Monitors section, note the following:
- Label – The name of the monitor.
- Probe Interval – The period of time between health checks of the IP host.
- 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.
- Headers – The request header name and value.
Create a Load Balancer Traffic Management Policy in Oracle Cloud Infrastructure
To create a new Traffic Management Load Balancer Policy in Oracle Cloud Infrastructure, see “To create a Load Balancer policy” in Managing Traffic Management Steering Policies.
Review the following information before replicating your Load Balancer policy in Oracle Cloud Infrastructure:
- Retries – The Retries field in Dyn Traffic Director lets users increase the number of health check locations for a wider range of vantage points. This increases the number of monitoring probes overall, providing greater accuracy. Increasing the Timeout value in Oracle Cloud Infrastructure Traffic Management allows more time for the probes to receive a response from endpoints.
- 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.
- Protocols – If you are using TCP or SMTP monitoring in Traffic Director, you will need to leverage either HTTP/s or Ping in Oracle Cloud Infrastructure Traffic Management.
- Serve Count– In Oracle Cloud Infrastructure Traffic Management, serve count can only be set to a value of 1 for Failover, Geolocation, and Prefix/ASN templates; however, the load balancing template can be increased above 1. For users that require an increased serve count on their policies, it is recommended that you manage the serve count using the API, where custom templates can be leveraged. Contact email@example.com for alternative implementations during migration. Once fully migrated, contact support.oracle.com.
- Min Eligible – Currently, the Min Eligible value cannot be defined in the Oracle Cloud Infrastructure Steering policy templates.
Note: For Oracle Cloud Infrastructure Traffic Steering, the Min Eligible value (the number of healthy endpoints for a pool to remain available) is locked at 1 at this time.
Use the following table to identify equivalent information in Oracle Cloud Infrastructure. Dyn Traffic Director includes some fields that are not available in the Traffic Management Steering service.