Provider pair
AWS Route 53 + OCI DNS: one DNS zone on both
Run the same zone on Route 53 and OCI DNS 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
- Route 53: the apex NS is rewritten to list the nameservers of every provider.
- OCI DNS: the apex NS is rewritten to list the nameservers of every provider.
- Features that only one provider has (for example Route 53 alias records and routing policies) are outside the canonical zone. The zone's capabilities are the intersection of both providers.
Set it up
- Connect AWS Route 53 with an IAM access key (permission guide).
- Connect OCI DNS with an API signing key of an OCI user (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 |
|---|---|---|
| AWS Route 53 | Inline IAM policy with CreateHostedZone, DeleteHostedZone, ListHostedZones, GetHostedZone, GetChange, ListResourceRecordSets and ChangeResourceRecordSets. | Inline IAM policy scoped to one hosted zone ARN: GetHostedZone, ListResourceRecordSets, ChangeResourceRecordSets, plus GetChange on change ARNs. No ListHostedZones. |
| 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. |
Good to know about each provider
AWS Route 53
- Alias records and routing policies (weighted, latency, geolocation) are Route 53-only; RedundantDNS leaves them alone and never touches the SOA.
- An optional CloudWatch statement lets RedundantDNS read query counts for managed-mode billing and usage charts.
OCI DNS
- Record sets are updated one at a time, idempotently. The SOA is never touched.
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 |
|---|---|---|
| AWS Route 53 | $0.50 per zone per month (first 25), then $0.10 | $0.40 per million (first billion), then $0.20 |
| OCI DNS | no per-zone charge | $0.85 per million, with a monthly free allowance (check Oracle’s page for the exact allowance) |
Related pairs
Put your zone on Route 53 and OCI DNS
Start with a 30-day trial: one zone on two providers you already have, no card. Plans from $9 a month after that.