I want Cloudflare to remain the source of truth for my public DNS, including DNSSEC and records published by PowerDMARC, but I'd also like a secondary DNS provider or downstream copy for redundancy. Ideally, both providers would be authoritative so the domain continues resolving if Cloudflare has an outage. What tools or architectures support this, and are there any limitations around zone transfers, API-based updates, or CNAME delegation?
5 Answers
What you’re describing is usually called secondary DNS or public DNS delegation. A secondary provider receives a copy of the authoritative zone, often through zone transfers or a provider-specific sync mechanism. You then publish nameservers from both providers at the registrar so either service can answer queries. Check whether Cloudflare supports the exact primary-to-secondary arrangement you need, since some hosted DNS platforms are designed to be the primary rather than provide traditional outbound transfers.
DNSControl provides a similar setup. It can manage Cloudflare and Azure DNS from one configuration and keep the zones synchronized. This works well if you’re comfortable treating a configuration file and deployment process as the authoritative source for DNS changes.
If the goal is only disaster recovery, a synchronized copy in another provider may be enough. Older services and some current DNS platforms can replicate changes into providers such as Route 53, with the backup zone kept ready to serve. Make sure the failover design includes DNSSEC key handling and that both providers can serve a consistent signed zone; otherwise the backup may not actually be usable during an outage.
For DMARC platforms, direct writes to Cloudflare often aren’t necessary. Many use CNAME delegation, where the DMARC-related record points to a name hosted by the vendor. That avoids giving the platform write access to your zone, but it is different from having the vendor push records directly through Cloudflare’s API. Confirm which model PowerDMARC supports and whether your requirement is about DNSSEC chain of custody or simply reducing the impact of a Cloudflare outage.
OctoDNS is worth looking at. It can manage the same records across multiple DNS providers, including Cloudflare, so you can publish the zone to more than one provider and choose nameservers from both. The tradeoff is that OctoDNS becomes the system managing the records rather than Cloudflare being the only source of truth.

Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures