Skip to content
dnsmigrator

deSEC AdGuard Home

Migrate DNS from deSEC to AdGuard Home.

3 record types move as they are. 1 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

A typical deSEC zone at AdGuard Home

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

deSEC AdGuard Home

  • ExactA@

    192.0.2.70

  • ExactAAAA@

    2001:db8::70

  • 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.

  • TranslatedCNAMEwww

    example.com.

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

How the move works

  1. 1

    Connect deSEC

    Connect deSEC with read-only access (API token).

  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 deSEC 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 deSEC

  • The minimum TTL is 3600 seconds for most domains (deSEC sets it per domain) and the maximum is 86400.
  • ALIAS/ANAME records and apex CNAMEs aren't supported; use A/AAAA or HTTPS records at the apex.
  • Every zone is DNSSEC-signed automatically. Give the DS records to your registrar to complete the chain.

Access we need: Any token can read all RRsets. Applying needs write permission on the RRsets (token policies can restrict it); creating zones needs perm_create_domain.

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 deSEC 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 deSEC?

No. We never write to deSEC. 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