[ryantownsend]

Can anyone comment on the best way to run multiple DNS services?

Is this as simple as setting up the same records on multiple providers and updating your nameservers to point to the different providers? Or is there more involved?

Are there any providers which will replicate records from your 'master' provider, or is this going to be manual?

[cpach]

DJB suggests using rsync over ssh: https://cr.yp.to/djbdns/tcp.html#intro-axfr

But I guess this excludes many of the popular DNS services that are used today.

[kchoudhu]

I have an ansible script that ships all my zone files around. Functionally equivalent, I suppose.

[cpach]

Smart!

[dozzie]

From operational point of view DJB always recommended ridiculous things.

[cpach]

Hehe. But for those running their own DNS servers this seems feasible, no?

[dozzie]

No. My domain uses five DNS servers under three different sysadmins. I can't possibly expect that fellow admins that were kind enough to run for me backup NS-es give me shell access to their systems.

[larrymcp]

We use BuddyNS (https://www.buddyns.com/) as our secondary DNS provider. They use AXFR to automatically sync their servers with your primary DNS servers.

You just need a primary DNS vendor which supports AXFR, such as DNS Park (https://www.dnspark.com/).

[keeperofdakeys]

To put it simply, yes. You have multiple NS records, and each points to a server that can act as an authoritative name server for your zone. When clients query for your zone from parent zones, they'll get all your name servers. The hard part is how you keep those name servers synchronised.

IIRC, bind has multiple built-in methods of keeping zone files synchronised between boxes.