Lorixen.
EN

Add a secondary DNS provider so your site survives an outage

Short answer: Your domain's DNS is usually hosted by a single company, so if that company has an outage, your website, online shop and email can all disappear at once even though your servers are fine. Adding a second authoritative DNS provider removes that single point of failure: both providers answer for your domain, and resolvers use whichever responds. You can set it up as a classic primary and secondary with zone transfers, or run two independent providers and push the same records to both. Either way, plan DNSSEC and any provider-only record types carefully before you switch.

Why one DNS host is a single point of failure

Every visit to your site starts with a DNS lookup. If the nameservers listed for your domain don't answer, browsers can't find your web server and other mail servers can't find yours. Cached answers keep some visitors working for a while, but once those expire, the site is effectively offline.

RFC 2182, the long-standing guide to choosing secondary DNS servers, makes the point directly: servers should be placed so that at least one is likely to be reachable for any likely failure, and putting them all in one place is "not a good policy". It also recommends servers in geographically distant locations, connected through diverse network paths. A single DNS company, however large, is still one operator, one set of software and one set of configuration changes.

Option 1: primary and secondary with zone transfers

In the traditional setup, one provider holds the editable zone (the primary) and the second copies it automatically (the secondary).

  • Zone transfer. The secondary pulls the whole zone using AXFR, which RFC 5936 defines over TCP, or incremental changes where both sides support them.
  • NOTIFY. RFC 1996 lets the primary tell secondaries the moment the zone changes, an "interrupt as opposed to poll" model, so updates spread quickly instead of waiting for the refresh timer.
  • Access control. Allow transfers only to your secondary provider's servers, ideally with a shared key, so strangers can't download your whole zone.

This works well when your primary provider supports outbound transfers and your secondary accepts inbound ones. Not every managed DNS service does, so check both before you commit.

Option 2: two independent providers

Some managed DNS services don't do zone transfers at all. The alternative is to treat both providers as primaries and send identical records to each, usually through their APIs or an infrastructure-as-code tool that manages DNS. Your source of truth becomes a file in version control, and a deploy updates both providers.

This approach has a catch: provider-specific features. Many hosts offer "ALIAS", "ANAME" or CNAME flattening at the root of the domain, geographic routing, or health-checked failover. These aren't standard record types, so they don't copy cleanly to another provider. Prefer plain A, AAAA, CNAME, MX and TXT records for anything that must exist on both sides, or confirm both providers support the same feature.

DNSSEC changes the plan

If your domain is signed with DNSSEC, both providers must serve answers that validate. With a primary and secondary, the simplest route is for the primary to sign and the secondary to serve the already-signed zone.

With two independent providers that each sign, RFC 8901 describes multi-signer models. In one, the providers share a common key-signing key set and each uses its own zone-signing keys; in the other, each has entirely separate keys. Either way, each provider's keys must be published by both, and key rollovers need coordination. If neither provider supports this, a temporary option is to run without DNSSEC during the migration, but that is a security decision to make deliberately, not by accident.

Switching over safely

Once both providers hold correct data, the change itself is small: list both providers' nameservers in your domain's NS records at your registrar.

A sensible order:

  1. Copy every record to the second provider and compare the two with lookups straight against each provider's nameservers. Missing records here (old TXT verification records, DKIM keys, SRV records for phone systems) are the usual surprise.
  2. Lower the TTL on your NS records ahead of the change if your provider allows it, so you can roll back faster.
  3. Update the NS set at the registrar to include both providers.
  4. Make sure the NS records inside both copies of the zone list the same full set of nameservers.
  5. Test from several networks and keep watching both providers for a few days.

Running it day to day

Redundancy fails quietly if the copies drift apart. Agree that all changes go through one path: the primary, or your version-controlled records file. Set up a scheduled check that queries both providers for key names (www, the root, MX, SPF and DKIM records) and alerts if answers differ.

Also check the SOA serial number on both sides after a change in a primary-secondary setup. If the secondary stops updating, it may keep serving old data until the zone expires, which can be worse than an obvious outage.

An illustrative example

An online homewares retailer in Brisbane runs its shop, booking calendar for in-store consultations and email on one domain, all on a single DNS host. After an evening when the shop was unreachable, the developer moves the records into a config file, deploys them to two DNS providers, replaces the root ALIAS record with A and AAAA records both providers support, and adds both nameserver sets at the registrar. A nightly script compares answers from both and posts any difference to the team chat.

FAQ

Does a secondary DNS provider make my website faster?

That isn't the goal. It's about staying reachable when one provider fails. Any speed difference depends on where each provider's servers are.

Can I use my registrar's free DNS as the second provider?

Possibly, if it accepts zone transfers or you can keep records in sync. Check its record types and whether it supports DNSSEC the way you need.

What happens if the two providers give different answers?

Visitors get inconsistent results depending on which server answered. That's why one change process and automated comparison matter.

Do I need this for a small business site?

If an evening offline would cost you orders or bookings, it's worth considering. If the site is a brochure, a single reliable provider may be enough.

If you'd like a second DNS provider set up without breaking email or DNSSEC, tell us where your domain's DNS is hosted today.

Sources

WhatsAppBook a call