# RedundantDNS > Multi-provider authoritative DNS: one DNS zone kept in sync on two or more providers (AWS Route 53, OCI DNS, Google Cloud DNS, Cloudflare; Azure DNS coming soon), with drift detection, probes and alerts. RedundantDNS keeps one canonical copy of each DNS zone and writes it to two or more authoritative DNS providers at once, as complete, independent copies. The NS set at the registrar lists the nameservers of every active provider, so if one provider stops answering, resolvers use the other and nobody notices. After every change it reads each provider back and compares it with the canonical zone: a record edited outside RedundantDNS shows up as drift, which is reconciled (the canonical zone wins) or adopted (the provider change becomes canonical). A standby provider can be kept in sync outside the NS set and promoted when needed. Delegation checks, probes and alerts watch every nameserver. Everything is available from the dashboard, the HTTP API (OpenAPI 3.1), the Terraform provider, the CLI and the MCP server for AI assistants such as Claude, with the same scopes, roles, IP allowlists and audit log. Deterministic by design: there is no model in the sync path. No AI or machine-learning component writes a record; every change is a diff in the zone journal that you can read, replay and audit. An AI assistant connected over MCP only calls the same API a person uses, within the scopes and role it was given. Dashboard and API: https://app.redundantdns.com. MCP server: https://app.redundantdns.com/mcp. The full text of the docs below, in one file: https://redundantdns.com/llms-full.txt. ## Docs - [MCP server: a guide for agents](https://redundantdns.com/docs/mcp.md): The RedundantDNS MCP server: connect Claude or any MCP client, scopes and the full tool list. - [HTTP API](https://redundantdns.com/docs/api.md): The RedundantDNS HTTP API: authentication, scopes, OAuth 2.1, alerts, webhooks and errors. - [The provider layer](https://redundantdns.com/docs/providers/README.md): How RedundantDNS abstracts DNS providers: the adapter contract, the two access levels, what each provider can serve and managed mode. - [MCP tool reference](https://redundantdns.com/docs/mcp-tools.md): Reference of every RedundantDNS MCP tool, generated from the server: scope, hints and input parameters. - [Connect Azure DNS](https://redundantdns.com/docs/providers/azure.md): Azure DNS is coming soon. How the connection will work: a service principal and DNS Zone Contributor on a group or one zone. - [Connect Cloudflare DNS](https://redundantdns.com/docs/providers/cloudflare.md): Connect Cloudflare DNS to RedundantDNS with a scoped API token, and how Cloudflare fits a multi-provider zone. - [Connect Google Cloud DNS](https://redundantdns.com/docs/providers/gcp.md): Connect Google Cloud DNS to RedundantDNS with a service account and a predefined or custom role. - [Connect OCI DNS](https://redundantdns.com/docs/providers/oci.md): Connect OCI DNS to RedundantDNS with an API signing key and a compartment or single-zone policy. - [RedundantDNS nameservers](https://redundantdns.com/docs/providers/rdns-ns.md): RedundantDNS nameservers - [Connect AWS Route 53](https://redundantdns.com/docs/providers/route53.md): Connect AWS Route 53 to RedundantDNS with a least-privilege IAM policy, at either access level. - [Connect your own nameserver (PowerDNS)](https://redundantdns.com/docs/providers/selfhost.md): Connect a nameserver you run yourself (PowerDNS Authoritative, HTTP API) as one more provider of a zone. ## Product - [RedundantDNS: multi-provider DNS, kept in sync](https://redundantdns.com/): One DNS zone, served by two or more providers at once: Route 53, OCI DNS, Google Cloud DNS, Cloudflare, Azure DNS soon. Kept in sync, verified and probed. - [How multi-provider DNS works](https://redundantdns.com/how-it-works): How DNS resolution works, how one zone is served by two providers, what happens on every change and during a provider outage, illustrated step by step. - [Manage DNS with Claude and AI agents: the MCP server](https://redundantdns.com/mcp): Connect Claude or any MCP client to RedundantDNS: create zones on two providers, check delegation, fix drift. Scoped tokens, roles and a full audit trail. - [Pricing](https://redundantdns.com/pricing): A 30-day trial on one zone and two providers, then Starter from $9 a month, Pro, Business and Enterprise. Managed provider accounts at cost plus 20%. - [Supported DNS providers and pairs](https://redundantdns.com/providers): Route 53, OCI DNS, Google Cloud DNS and Cloudflare, with Azure DNS coming soon: how each one fits a multi-provider zone, and every pair explained. - [Route 53 + OCI DNS: one DNS zone on both](https://redundantdns.com/providers/route53-oci): Run one DNS zone on AWS Route 53 and OCI DNS at the same time, kept in sync by RedundantDNS: permissions, caveats and costs for this pair. - [Route 53 + Cloud DNS: one DNS zone on both](https://redundantdns.com/providers/route53-gcp): Run one DNS zone on AWS Route 53 and Google Cloud DNS at the same time, kept in sync by RedundantDNS: permissions, caveats and costs for this pair. - [Route 53 + Azure DNS: one DNS zone on both (coming soon)](https://redundantdns.com/providers/route53-azure): Coming soon: one DNS zone on AWS Route 53 and Azure DNS at the same time, kept in sync by RedundantDNS. Azure DNS is not available yet. - [Route 53 + Cloudflare: one DNS zone on both](https://redundantdns.com/providers/route53-cloudflare): Run one DNS zone on AWS Route 53 and Cloudflare DNS at the same time, kept in sync by RedundantDNS: permissions, caveats and costs for this pair. - [OCI DNS + Cloud DNS: one DNS zone on both](https://redundantdns.com/providers/oci-gcp): Run one DNS zone on OCI DNS and Google Cloud DNS at the same time, kept in sync by RedundantDNS: permissions, caveats and costs for this pair. - [OCI DNS + Azure DNS: one DNS zone on both (coming soon)](https://redundantdns.com/providers/oci-azure): Coming soon: one DNS zone on OCI DNS and Azure DNS at the same time, kept in sync by RedundantDNS. Azure DNS is not available yet. - [OCI DNS + Cloudflare: one DNS zone on both](https://redundantdns.com/providers/oci-cloudflare): Run one DNS zone on OCI DNS and Cloudflare DNS at the same time, kept in sync by RedundantDNS: permissions, caveats and costs for this pair. - [Cloud DNS + Azure DNS: one DNS zone on both (coming soon)](https://redundantdns.com/providers/gcp-azure): Coming soon: one DNS zone on Google Cloud DNS and Azure DNS at the same time, kept in sync by RedundantDNS. Azure DNS is not available yet. - [Cloud DNS + Cloudflare: one DNS zone on both](https://redundantdns.com/providers/gcp-cloudflare): Run one DNS zone on Google Cloud DNS and Cloudflare DNS at the same time, kept in sync by RedundantDNS: permissions, caveats and costs for this pair. - [Azure DNS + Cloudflare: one DNS zone on both (coming soon)](https://redundantdns.com/providers/azure-cloudflare): Coming soon: one DNS zone on Azure DNS and Cloudflare DNS at the same time, kept in sync by RedundantDNS. Azure DNS is not available yet. - [Domain registration and transfer with multi-provider DNS](https://redundantdns.com/domains): Register or transfer domains in and get free DNS on our nameservers while the domain is live here. You stay the registrant and the auth code is self-service. - [How enterprise multi-provider DNS works](https://redundantdns.com/enterprise): Run the data plane in your own network, coming soon: provider credentials never reach us, the bucket is the only channel, licensing never takes DNS down. - [Security](https://redundantdns.com/security): How RedundantDNS protects provider credentials and zone data: per-organization encryption, KMS-wrapped keys, replicated storage, restore drills and least privilege. - [Use cases for multi-provider DNS](https://redundantdns.com/use-cases): SaaS uptime, agencies, compliance and DR, leaving a single provider, and enterprise self-hosting. - [DNS redundancy for SaaS uptime](https://redundantdns.com/use-cases/saas-uptime): Keep your SaaS reachable when one DNS provider fails: one zone served by two providers, kept in sync, with probes and alerts. - [Multi-provider DNS for agencies and MSPs](https://redundantdns.com/use-cases/agencies): Manage DNS for many client domains from one dashboard, on the clients’ own provider accounts, with per-organization isolation and an audit log. - [DNS for compliance and disaster recovery](https://redundantdns.com/use-cases/compliance-dr): Evidence that DNS survives a provider failure: two independent providers, continuous verification, nameserver probes and an audit trail. - [Move off a single DNS provider without downtime](https://redundantdns.com/use-cases/migrate-off-single-provider): Adopt the zone you already have, add a second provider next to it, and change the NS set when both agree. No cut-over weekend. - [Self-hosted multi-provider DNS for enterprises](https://redundantdns.com/use-cases/enterprise-self-hosted): Run RedundantDNS as one binary on your own infrastructure, with your own bucket and keys, or keep only the data plane in-house. - [Compare RedundantDNS](https://redundantdns.com/compare): RedundantDNS compared with octoDNS, DNSControl and secondary DNS from managed DNS vendors. - [RedundantDNS vs octoDNS](https://redundantdns.com/compare/octodns): octoDNS syncs a YAML zone to many DNS providers from your CI. RedundantDNS runs the same diff and apply as a service, with a dashboard, probes and alerts. - [RedundantDNS vs DNSControl](https://redundantdns.com/compare/dnscontrol): DNSControl pushes a JavaScript-defined zone to several providers from CI. RedundantDNS keeps the zone in sync continuously, with verification, probes and alerts. - [Multi-provider DNS vs secondary DNS](https://redundantdns.com/compare/secondary-dns): Secondary DNS copies a zone from a primary by zone transfer. Multi-provider DNS writes the zone to each provider through its API. Differences, limits and prices. ## Optional - [RedundantDNS Learn](https://learn.redundantdns.com/): the blog (DNS outage write-ups) and the technical guides, such as Cloudflare Registrar and multi-provider DNS. - [Terms of Service](https://redundantdns.com/terms): The RedundantDNS Terms of Service. - [Privacy Policy](https://redundantdns.com/privacy): The RedundantDNS Privacy Policy. - [Managed Provider Terms and Acceptable Use Policy](https://redundantdns.com/legal/managed-terms): The terms and acceptable use policy for zones served by provider accounts that RedundantDNS runs (managed mode). - [RedundantDNS Nameservers Terms](https://redundantdns.com/legal/nameservers-terms): The terms for zones served by the RedundantDNS nameservers, the authoritative nameservers RedundantDNS operates itself. - [Contact](https://redundantdns.com/contact): Talk to the RedundantDNS team about a plan, an enterprise install, security or anything else.