A question we frequently receive is: “How can I manually fail traffic over from my primary server to my failover server group in the Cloud Load Balancer?” Manually failing traffic is something you may wish to do if your primary server is experiencing issues that the monitor has not yet detected, or if you want […]
The “failover after” setting (shown below) in the main Failover Pool configuration is the number of our cloud nodes (datacenters) that must see your server as DOWN before actually failing over. All of our datacenters monitor your servers all the time. This setting simply allows you to increase the reliability of the results before action […]
When creating a failover pool in DNS Failover you are given the opportunity to specify a monitor for each IP address that is a member of the pool to detect whether or not the IP is available (online) and can be used for the corresponding ‘A’ or ‘AAAA’ record when required. To recap, in roundrobin mode, […]
We support two different DNS Failover methods. Sequential and Round Robin. Sequential Method: This method uses the server IP addresses one by one in the order they are entered. That way, you always have one IP address announced for your ‘A’ record, which is considered a primary server. Should that server go offline, the failover […]
When you have created a DNS Failover pool and have assigned it to an ‘A’ or ‘AAAA’ record, you want the flexibility to switch back and forth between the available servers during outages. To best accomplish this, we highly recommend decreasing the TTL value for that particular DNS record to the lowest allowable setting of […]
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 […]
How can I reliably monitor my database server to see if it is online, or in the case of a replicated database, if it is the primary or not?
The recommended way to monitor any type of database, including Microsoft SQL Server, is to create a hidden web-page that does a specific database query, and when successfully completed, sends a word (e.g. “OK”) to the web browser. This method is secure because you need not open SQL ports in your firewall to allow our […]
If the table in the Failover tab indicates that a server other than the primary server is “in use”, DNS records have been updated and failover has occurred. If you attempt to ping the host associated with the failover record and you still get the old IP, here are a few things to look at: […]
Does DNS Failover have a feature to prevent the primary IP from being put back into service when it comes back online?
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, our DNS failover service was designed to easily support manual failover. Often customers wish to test their failover site on a periodic basis, or they wish to redirect traffic during a maintenance window. To do this within the portal, open up the Failover Entry, and simply uncheck the “Active” checkbox as shown below. This will immediately […]