What is round robin?
For an explanation of round robin configuration, please visit our tutorial here.
What is DNS Failover?
The DNS Failover service from DNS Made Easy is used to keep sites and web services online in the event of system or network issues. This is done by moving DNS traffic to another IP address that you have running at another location. This service can also be used to migrate traffic between redundant internet connections. A DNS Failover configuration with round robin will split traffic evenly between hosts unless one of the hosts is offline in which case it would be removed from the round robin pool.
Here is how the DNS Failover services works:
DNS Failover services are configured on A records which point to IP addresses. DNS Made Easy’s monitoring nodes check your primary IP address on a 2 to 4 minute monitoring window. You can setup the monitoring servers to check if your service is running on either TCP, UDP, HTTP, or HTTPS protocols, and on any port. As soon as your primary server fails to respond from at least two different geographic monitoring locations, your DNS is instantly updated on all DNS Made Easy name servers globally to point a secondary IP address as long as it does respond on the same port and protocol configured. You can specify up to 5 IP addresses for each of your host names.
The steps to configure DNS Failover are as follows:
- Access the DNS Records for your domain
- Add round robin A records (if they do not exist already)
- Add a Contact List (if one does not exist already)
- Configure Failover
|USER ACTION 1: Access the DNS Records for your domain||WHAT YOU WILL SEE|
|1. Select the “DNS” Menu, select “Managed DNS”|
|2. Select a domain from the either the “Recently Updated Domains” box, or start typing the domain name in the text box on the “Select Domain” tab|
|USER ACTION 2: Add a round robin record||WHAT YOU WILL SEE|
|1. If and A record does not already exist for the desired name, then under “A Records” click the plus sign to add a new A record.|
|2. We will add a root record (an A record with the name field left blank) to the domain example.com with an IP address of 126.96.36.199 and a TTL of 180 seconds. If you are adding DNS Failover to an existing A record, then you will want to edit the TTL of this record to set it to a lower value. Records which use DNS Failover services should have a TTL between 180-300 seconds. Click “Submit”What is a TTL?|
|Now, we will add a second round robin A record with an IP address of 188.8.131.52 and a TTL of 180 seconds. At this point in the configuration, traffic to example.com is split 50/50 between 184.108.40.206 and 220.127.116.11. Click “Submit”|
|USER ACTION 3: Add a Contact List||WHAT YOU WILL SEE|
|1. Now we will set up a contact list for notification of the failover event. Select the “Config” menu, Click on “Contact Lists”|
|2. Click on the plus sign (+) to add a new contact list|
|3. Give the contact list an identifiable name and enter the email address(es) you would like included in the list, one per line. Click “Submit”Note: Groups are discussed in a separate tutorial here, however if you are the only user for your account your contact list should be part of the “Default” group. Otherwise, it should be part of whatever group is set up to have management permissions for the domain.|
|USER ACTION 4: Configure Failover||WHAT YOU WILL SEE|
|1. Now we set up DNS Failover. IMPORTANT NOTE: The System Monitoring and DNS Failover options configured in this portion of the tutorial are examples only. Each configuration will differ based on monitoring requirements. Select the DNS Menu, select “Managed DNS”|
|2. Select a domain from the either the “Recently Updated Domains” box, or start typing the domain name in the textbox on the “Select Domain” tab|
|3. Under the “SM / FO” column next to the A record, click “off” to edit the configuration.|
|4. Enable System Monitoring and/or DNS Failover by checking the boxes. These can be used independently of one another if you wish.|
|5. Provide a “System Description” – this will be included in the notification you receive so you know which system the notification is for.|
|6. Select your contact list to be notified of IP statuses or changes – We select the one we created. The default notification is to the “Account Owner” which is the email address on file for the account (you can view this under the Config – Users menu).|
|7. Select a maximum number of emails you would like to receive regarding each system monitoring and/or failover event|
|8. Select a Sensitivity Level – The “sensitivity” option in DNS Failover allow you to specify different numbers of checks the monitoring locations will make against the IP. High Sensitivity means less checks, three checks are made in immediate succession of one another to confirm the status of the server. Medium Sensitivity (which is the default) performs six immediate checks. Low Sensitivity performs nine immediate checks. The lower the sensitivity level, the more confirmations the monitoring servers will make.|
|9. Configure a port and protocol to monitor based on what criteria you want to confirm is reachable on your server. In the example here we are configuring the primary IP address of 18.104.22.168 to be monitored on HTTP port 80 and failing over to the IP address 22.214.171.124 if the primary is not available.|
|10. Enter the fully qualified domain name of the system you are monitoring. This is the full host name of the monitored system.|
|11. This is optional. We have also added a file and string to query for in the HTTP configuration (this is only example data), these fields are optional with an HTTP or HTTPS configuration. The system will query http://126.96.36.199:80/index.html and look for the string of UP in the first 1KB of text on that page. All this criteria must be met for the IP to be considered online. In addition, the web server must reply with a 200 response code.|
|12. This is optional. We have also enabled the “Turn off auto-failover after first failure” feature with a check mark. This means that DNS Failover will not revert traffic back to the primary IP address automatically. The current IP will remain 188.8.131.52 until it is manually edited it back to 184.108.40.206.|
|14. Configure the same settings for the second A record with an IP of 220.127.116.11. We are configuring the primary IP address of 18.104.22.168 to be monitored on HTTP port 80 and failover to the IP address 22.214.171.124 if the primary is not available. Now, if 126.96.36.199 is not available 100% of traffic will be sent to 188.8.131.52 and if 184.108.40.206 is not available 100% of traffic will be sent to 220.127.116.11. If both IP addresses are available traffic will be split 50/50 between 18.104.22.168 and 22.214.171.124.|
For your information, below is the list of networks our monitoring services will check your primary IP address from: