Self-hostedDNS hostingCapabilities verified
AdGuard Home
Migrate DNS zones to or from AdGuard Home: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at AdGuard Home. Free and read-only.
Access we need
- Credentials
- Server URL + web interface username + password (HTTP Basic)
- Permissions
- AdGuard Home has a single admin role, so the account can read and change all settings; there is no read-only login.
Runs on your own infrastructure.
We connect to its API over the internet, so the API endpoint must be reachable on a public address over HTTPS. We never connect to private or internal addresses.
What AdGuard Home supports
The same data the translation engine uses when it plans a migration.
- Create zones through the API
- List zones through the API
- Turn on DNSSEC through the API
- Apex CNAME (flattening)
- Apex ALIAS record
- Aliases to cloud resources
- CDN proxy on records
- Routing policies
- Minimum TTL
- 300s
Record types
- A
- AAAA
- CNAME
- ALIAS
AdGuard Home-only records
- ADGUARDHOME_A_PASSTHROUGH
- ADGUARDHOME_AAAA_PASSTHROUGH
These have no equivalent elsewhere and are flagged in every preview.
Good to know
- 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.