The DNS Failover Service determines a server is down based on the monitoring type you’ve selected and configured. For example, if you’ve created a PING monitor and assigned that to your server, as soon as it stops pinging and exceeds the test “interval” and “retries” values you’ve specified, it will be considered “down” and subject […]
Yes. Our DNS Failover does have a feature to prevent “Auto Rejoin”. Unchecking this box (shown below) for any of your servers will prevent it from automatically being used again when it comes back online. This is often necessary if, after a fail over, you need to synchronize back-end data (such as a database) to the primary […]
Yes, absolutely. You can easily use our DNS Failover solution without moving your entire domain to our platform. While it may be preferable to move your domain so all DNS management is in one interface, we understand that this is not always possible. To use Failover, three steps must be completed: 1: Configure Failover First, you must […]
Yes, absolutely. This is a very common use for our DNS Failover service. While some customers use it to switch between servers at different datacenters, it works very well to switch between the same server that has two different public IP addresses at the same location or datacenter (e.g. two ISPs, two WAN connections etc.) DNS […]
Dealing with a DNS cache is probably the largest challenge of a DNS failover service. Even when setting the TTL for your ‘A’ record to a very low number, certain ISPs or networks just like to ignore those TTLs and elect to set the cache for a value that they deem appropriate. AOL is a prime […]
Yes, absolutely! The DNS Failover service supports a multitude of different monitoring types that you can create and assign to two of the different servers in your failover pool. Each server can use a ‘global’ monitor you configure for the pool, a unique custom monitor, and it can even be set to skip monitoring altogether, […]
The similarities Both solutions require that you tell us what the IP address(es) are for your ‘real servers’. That way we know how to alter DNS or route traffic when one or more servers go up or down. These IP addresses must be publicly accessible, not private. Also, both solutions use the same type of […]
Want to quickly understand how DNS Failover works? We’ve created an infographic that explains it in a few simple steps… plus a detailed look at our user interface. (Click on the image to enlarge it, and then click to expand it.)
When implementing a failover solution, the most common questions we receive are: How can we architect a failover solution for our application? How quickly can we failover from the primary site to the secondary site? How quickly can it fail back when the primary comes back online? Is there a way to prevent automatic failback […]
Over the years, DNS Failover has become a very popular service primarily due to the fact that it is relatively inexpensive and fairly easy to deploy and manage. But is it the right solution for your organization? In this article, we’ll outline what DNS failover is and provide an overview of the benefits and appropriate uses for […]