Skip to content
dnsmigrator

Amazon Route 53 AdGuard Home

Migrate DNS from Route 53 to AdGuard Home.

3 record types move as they are. 3 things work differently at AdGuard Home, and the preview shows exactly which of your records they affect.

Free preview. Read-only. Nothing changes until you apply.

What works differently

Generated from the same provider capability data the migration engine uses.

Moves as-is

  • A
  • AAAA
  • CNAME

Routing policies are flattened

AdGuard Home has no routing policies. Weighted, geo and latency sets collapse into one set of answers, and failover keeps only the primary. Each one is flagged for review.

TTLs below 300s are raised

AdGuard Home's minimum TTL is 300 seconds. Shorter TTLs are raised to 300s and shown as translated.

A typical Route 53 zone at AdGuard Home

Example records for example.com. Open any flagged row to read why it changed.

Route 53 AdGuard Home

  • TranslatedALIAS@

    d1a2b3.cloudfront.net.

    Stored as a AdGuard Home ALIAS record to d1a2b3.cloudfront.net.

  • UnsupportedMX@

    Not migrated

    AdGuard Home doesn't support MX records through its API.

  • UnsupportedTXT@

    Not migrated

    AdGuard Home doesn't support TXT records through its API.

  • UnsupportedCAA@

    Not migrated

    AdGuard Home doesn't support CAA records through its API.

  • UnsupportedTXT_dmarc

    Not migrated

    AdGuard Home doesn't support TXT records through its API.

  • UnsupportedSRV_sip._tls

    Not migrated

    AdGuard Home doesn't support SRV records through its API.

  • ReviewAapi

    192.0.2.10 +1

    Weighted routing isn't available at the destination. All 2 answers are served together as simple round-robin.

  • UnsupportedSPFlegacy

    Not migrated

    SPF record type is obsolete. Stored as TXT, which is what mail servers read.

  • TranslatedCNAMEwww

    example.com.

    TTL 3600s is outside the allowed range. Set to 300s.

How the move works

  1. 1

    Connect Route 53

    Connect Route 53 with read-only access (Cross-account IAM role with an external ID).

  2. 2

    Connect AdGuard Home

    Connect AdGuard Home (Server URL + web interface username + password (HTTP Basic)). Write access is only used when you apply.

  3. 3

    Review the preview

    Check every record marked Review or Unsupported. Each one explains what changes and why.

  4. 4

    Apply to AdGuard Home

    We snapshot the AdGuard Home zone, write in batches, and leave Route 53 untouched.

  5. 5

    Verify

    We query AdGuard Home's own nameservers for every record and compare the answers before you switch.

  6. 6

    Switch nameservers

    Lower TTLs a day or two ahead, remove any DS record if DNSSEC is on, then point the domain at the new nameservers at your registrar.

Good to know about Route 53

  • Alias records can only target AWS resources or records in the same hosted zone.
  • Weighted, latency, geolocation and failover routing are Route 53 features. Most other providers can't reproduce them.
  • Apex CNAMEs are not allowed. Use an alias record instead.

Access we need: route53:ListHostedZones, GetHostedZone, ListResourceRecordSets for the preview; ChangeResourceRecordSets and CreateHostedZone to apply.

Good to know about AdGuard Home

  • AdGuard Home usually runs on a private network; we refuse private addresses by design, so it is only reachable if you expose its web interface publicly over HTTPS.
  • Only DNS rewrites are managed: A, AAAA, CNAME (ALIAS at the apex) and the A/AAAA passthrough rules. Rewrites have no per-record TTL (the server uses one global TTL), so we report 300 seconds as DNSControl does.
  • AdGuard Home has no zones. We group rewrites by the domains you list, or by the last two labels of each name.

Access we need: AdGuard Home has a single admin role, so the account can read and change all settings; there is no read-only login.

Questions

Will there be downtime moving from Route 53 to AdGuard Home?

Not if both providers serve the same answers during the switch. The records are copied to AdGuard Home and verified before you change nameservers, so resolvers get the same answer from either side while caches expire.

Do I have to delete anything at Route 53?

No. We never write to Route 53. Keep the old zone for a week after cutover so you can switch back instantly if anything looks wrong.

What about DNSSEC?

If DNSSEC is on, remove the DS record at your registrar and wait for it to expire before switching nameservers. Then enable DNSSEC at AdGuard Home and publish its new DS record. The cutover plan walks you through each step.

Related migrations

Ready to see your own zone?

Start a free preview