DNS Failover for Fast Recovery
If your server goes down, visitors reach your backup instead of an error page. Our engineers set it up and watch it for you.
When a health check fails, DNS answers update immediately. Resolvers follow within the low TTL.
Our nameservers run on Cloudflare’s global network, so updated answers reach resolvers everywhere, fast.
HTTP, HTTPS, TCP, and ICMP checks probe your servers from multiple regions, every 60 seconds by default.
Covers a primary and a backup endpoint. Setup and support from our engineers are included.
Features
Failover is one DNS change: the failing server drops out of the answer, and visitors land on the backup instead.
Multi-region health checks
Probes test each endpoint over HTTP, HTTPS, TCP, or ICMP every 60 seconds by default, with faster intervals available. Checks run from several regions at once, so one flaky network path cannot trigger a false failover.
Works with servers anywhere
Failover happens at the DNS level, so it protects servers on Togglebox, in your office, or in another cloud. When the primary recovers, failback is automatic or held for your approval, whichever you choose.
Managed on Togglebox DNS
Your domain uses our nameservers, and we handle that changeover during setup. We configure the monitors and thresholds with you and notify you when a failover fires.
Pricing
- DNS Failover (primary + backup)
- $5 /mo
- Additional endpoints
- $5 /mo · each
- Setup & DNS changeover
- Free
Powered by Cloudflare load balancing at Cloudflare’s own price. Our engineers handle setup, the DNS changeover, and support.
Common Questions
What does DNS Failover do?
DNS Failover watches your configured endpoints and changes DNS answers when the active endpoint is unhealthy. Visitors are directed to a healthy server or recovery target without manually editing DNS during an outage.
Do my servers need to be hosted with Togglebox?
No. Failover happens at the DNS level, so it protects servers running anywhere: on Togglebox, in your office, or in another cloud. The one requirement is that your domain uses Togglebox nameservers, which run on Cloudflare’s global network. We handle that changeover during setup.
How are health checks configured?
Checks probe each endpoint over HTTP, HTTPS, TCP, or ICMP from multiple regions, every 60 seconds by default; faster intervals are available. We confirm what a healthy response looks like before enabling failover.
How fast does DNS failover happen?
Failover speed depends on the health-check interval, failure threshold, and DNS TTL used by resolvers. We tune the TTL and checks for fast recovery while avoiding unnecessary flips from short network blips.
What happens when the primary server recovers?
Failback can be planned around your application. Some workloads should return automatically after the primary passes checks; others should stay on the recovery target until you approve the switch back.
Is DNS Failover the same as Disaster Recovery?
No. DNS Failover redirects traffic to a healthy endpoint. Disaster Recovery protects the server data and recovery process. Many production designs use both: DR to restore systems and DNS Failover to steer traffic.
What do you need to set up DNS Failover?
We need the domain or hostname, primary and backup endpoints, preferred health-check path, expected healthy response, and whether failback should be automatic or engineer-approved. If your domain is not on Togglebox nameservers yet, we move it during setup.
No matching questions found.
Ready to set up DNS failover?
Tell us which servers need protection and how you want failover to work. We will configure the checks and move your DNS.