Provider pair
OCI DNS + Cloudflare DNS: one DNS zone on both
Run the same zone on OCI DNS and Cloudflare at once. RedundantDNS writes every change to both, verifies them and probes their nameservers, and the NS set at your registrar lists both, so either one can answer.
How this pair behaves
- OCI DNS: the apex NS is rewritten to list the nameservers of every provider.
- Cloudflare: the apex NS is rewritten to list the nameservers of every provider, with Cloudflare’s Multi-provider DNS setting on (RedundantDNS turns it on when it attaches the zone).
- Both OCI DNS and Cloudflare serve the full nameserver plan at the apex: RedundantDNS turns on Cloudflare’s Multi-provider DNS setting when it attaches the zone.
- This needs a registrar where you can edit the NS set. A domain registered at Cloudflare Registrar stays on Cloudflare’s nameservers only; see the note below.
- The zone accepts TTLs from 60 seconds to one day, the range Cloudflare supports.
- Features that only one provider has (for example provider-specific routing) are outside the canonical zone. The zone's capabilities are the intersection of both providers.
Registered at Cloudflare Registrar?
Cloudflare Registrar only allows Cloudflare’s nameservers, so the apex of a domain registered there cannot be on OCI DNS too. Subdomains such as api. can, with no transfer, and the apex can once the
registration moves to another registrar.
Set it up
- Connect OCI DNS with an API signing key of an OCI user (permission guide).
- Connect Cloudflare DNS with an API token (permission guide).
- Create the zone in RedundantDNS, or adopt the one you already have on either provider.
- Attach both connections. RedundantDNS creates or adopts the zone on each and applies the records.
- Set the NS records at your registrar to the nameservers of both providers, as the dashboard lists them. The delegation check tells you when it is live.
Permissions, per access level
Pick the level per connection. The guides have the exact policies and roles to copy.
| Provider | Create and manage zones | Manage an existing zone |
|---|---|---|
| OCI DNS | Policy "manage dns" on one compartment: create zones there, write records and apex NS, delete on detach. | Policy "use dns" with a condition on one zone OCID: read the zone and update its records, nothing else. |
| Cloudflare DNS | Custom API token with Zone · Zone Edit and Zone · DNS Edit on one account. | Custom API token with Zone · Zone Read and Zone · DNS Edit on one specific zone. |
Good to know about each provider
OCI DNS
- Record sets are updated one at a time, idempotently. The SOA is never touched.
Cloudflare DNS
- RedundantDNS turns on Cloudflare’s Multi-provider DNS setting when it attaches a zone. With it on, Cloudflare honors the NS records at the apex and activates the zone even though the registrar also lists other providers’ nameservers.
- Domains registered at Cloudflare Registrar can only use Cloudflare’s nameservers, so their apex cannot be multi-provider while they are registered there. Subdomains can. Cloudflare Registrar guide
- Records are always written with the proxy off (DNS only), so every provider answers the same addresses. TTLs must be between 60 seconds and one day.
What the providers charge
With your own accounts you pay the providers directly and RedundantDNS charges only its plan. In managed mode these costs are passed through at cost plus 20%, line by line. Public list prices, collected on 2026-09-23; check the providers’ pages before relying on them.
| Provider | Per zone | Queries |
|---|---|---|
| OCI DNS | no per-zone charge | $0.85 per million, with a monthly free allowance (check Oracle’s page for the exact allowance) |
| Cloudflare DNS | free on the Free plan (DNS) | free |
Related pairs
Put your zone on OCI DNS and Cloudflare
Start with a 30-day trial: one zone on two providers you already have, no card. Plans from $9 a month after that.