BIND zone file PowerDNS Authoritative
Import a zone file into PowerDNS Authoritative.
23 record types move as they are. 2 things work differently at PowerDNS, 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
- MX
- TXT
- NS
- SRV
- CAA
- PTR
- DS
- HTTPS
- SVCB
- TLSA
- SSHFP
- NAPTR
- SPF
- CERT
- URI
- DHCID
- DNAME
- OPENPGPKEY
- RP
- SMIMEA
LOC isn't available
TTLs below 1s are raised
A typical Zone file zone at PowerDNS
Example records for example.com. Open any flagged row to read why it changed.
Zone file PowerDNS
- ExactA@
192.0.2.60
- ExactMX@
10 mx1.mail.example.net. +1
- ExactTXT@
"v=spf1 include:_spf.example.net -all"
- ExactCAA@
0 issue "letsencrypt.org"
- ExactTXT_dmarc
"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
- ExactSRV_sip._tls
100 1 443 sip.example.net.
- ExactAfast
192.0.2.61
- ExactSSHFPssh
4 2 9d97e98f8af710c7e4f3b5b0b1f1b8c0c7e2a4b8c5a0e3b1f8d2c7a9b0e1f2a3
- ExactCNAMEwww
example.com.
| Status | Type | Name | At PowerDNS | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 1h | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | A | fast |
| 30s | |
| Exact | SSHFP | ssh |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect Zone file
Paste or upload the zone file you want to move.
- 2
Connect PowerDNS
Connect PowerDNS (API URL + API key (X-API-Key) + server ID). Write access is only used when you apply.
- 3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
- 4
Apply to PowerDNS
We snapshot the PowerDNS zone, write in batches, and leave Zone file untouched.
- 5
Verify
We query PowerDNS's own nameservers for every record and compare the answers before you switch.
- 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 Zone file
- Zone files can't express provider features like proxying, alias records or routing policies.
Access we need: No credentials. Everything stays in your browser until you choose to save it.
Good to know about PowerDNS
- We only connect to public HTTPS addresses: expose the PowerDNS webserver through a reverse proxy with TLS and allow-list our egress IPs; private or internal addresses are refused.
- ALIAS records only resolve if expand-alias and a resolver are configured on the server, and DNAME needs dname-processing.
- Disabled records are not imported, and an RRset we update is replaced as a whole, so disabled entries inside it are dropped.
Access we need: The PowerDNS API key grants full read/write access to every zone on the server; there is no read-only key. Restrict it with webserver-allow-from.
Questions
Will there be downtime moving from Zone file to PowerDNS?
Not if both providers serve the same answers during the switch. The records are copied to PowerDNS 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 Zone file?
No. We never write to Zone file. 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 PowerDNS and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview