Local DNS zone file and record text checker

DNS Zone File Checker for local DNS migration QA before you change nameservers

Paste a DNS zone file, Cloudflare DNS export or bulk DNS records into this DNS Zone File Checker before a migration. DNS zone files are checked locally in your browser. They are not uploaded. The page checks record syntax and migration risks; it does not run live DNS propagation, global node monitoring or DNS history lookups.

DNS Zone File Checker local-only review

Run the DNS Zone File Checker

Use the DNS Zone File Checker for BIND-style zone files, Cloudflare DNS exports and pasted DNS record batches. It checks A, AAAA, CNAME, MX, TXT, NS, SOA and CAA records in the browser and highlights problems that often break DNS migrations.

-

DNS zone files are checked locally in your browser. They are not uploaded.

This DNS Zone File Checker does not perform real-time DNS propagation checks, global node tests or DNS history queries because those require multi-region servers, external databases or continuous crawling.

Try DNS Zone File Checker samples

DNS Zone File Checker results will appear here

Paste records to see record type statistics, invalid lines, CNAME conflicts, MX priority gaps, TXT quote issues, duplicate SPF, wrong DMARC and DKIM hostnames, abnormal TTLs, wildcard risk, root @ notation, trailing-dot issues and copyable repair suggestions.

DNS Zone File Checker workflow for local DNS migration review

The DNS Zone File Checker turns pasted DNS record text into grouped findings before you import records or change nameservers.

Paste records into the DNS Zone File Checker

Paste a BIND zone file, Cloudflare DNS export or bulk DNS records and keep the entire review inside your browser.

Check zone file Read the guide
DNS Zone File Checker interface with pasted zone file records and local record type statistics

Review DNS Zone File Checker migration risks

See invalid lines, CNAME conflicts, missing MX priority, TXT quotes, duplicate SPF, DMARC and DKIM hostnames, TTLs, wildcards and trailing dots.

Review results Browse tools
DNS Zone File Checker results showing migration risks and copyable fix suggestions

Copy DNS Zone File Checker fix suggestions

Use copyable suggestions as a migration checklist while remembering that live propagation, global nodes and DNS history are outside the local scope.

Copy fixes Open directory
DNS Zone File Checker local workflow from Cloudflare export to copyable fixes

DNS Zone File Checker features for record text QA

This DNS Zone File Checker focuses on browser-local parsing and practical migration risks, not network-dependent DNS intelligence.

Record type statistics

Count A, AAAA, CNAME, MX, TXT, NS, SOA and CAA records so you can quickly spot missing or unexpected groups.

Check records

Conflict and syntax checks

Find invalid lines, CNAME coexistence conflicts, missing MX priority, malformed A or AAAA values and incomplete SOA or CAA rows.

Find conflicts

Email DNS migration risks

Catch duplicate SPF TXT records, DMARC records outside _dmarc and DKIM TXT records outside selector._domainkey before import.

Review email DNS

TTL and wildcard review

Flag unusually low or high TTL values and wildcard records that could catch unintended hosts after a migration.

Review TTL

Provider import cleanup

Highlight root @ notation and missing trailing dots so records are easier to move between DNS providers.

Clean imports

Local-only boundary

Keep the DNS Zone File Checker focused on pasted text and avoid data-heavy propagation, node or history claims.

Read limits

How to use the DNS Zone File Checker

Use the DNS Zone File Checker before importing DNS records into a new provider, changing nameservers or cleaning up a Cloudflare export.

01

Paste the zone text

Paste a DNS zone file, Cloudflare DNS export or DNS record batch. Include $ORIGIN and $TTL when available so @, relative names and TTL review are clearer.

  • Use the same export you plan to import
  • Keep comments if they help humans, but they are ignored by the parser
  • Review one zone at a time for cleaner results
Paste records
02

Review grouped findings

Start with invalid record lines, CNAME conflicts, MX priority, duplicate SPF and wrong DMARC or DKIM hostnames. Then review TXT quotes, TTL, wildcard, @ and trailing-dot items.

The DNS Zone File Checker is a migration QA helper. It checks pasted text, not the live public DNS state.

Review findings
03

Copy repair suggestions

Copy the fix list into your change plan, adjust records in your DNS provider and run the DNS Zone File Checker again before import or cutover.

  • Keep one SPF record per owner
  • Keep CNAME records alone
  • Use provider-specific values for final MX, DKIM and verification records
Copy fixes

DNS Zone File Checker FAQ

Answers about DNS Zone File Checker privacy, accepted input, local accuracy, migration limits and what to do with failed checks.

Are DNS zone files uploaded by the DNS Zone File Checker?

No. DNS zone files are checked locally in your browser. They are not uploaded. The page parses the pasted text and creates findings in the frontend.

What input can I paste into the DNS Zone File Checker?

You can paste BIND-style DNS zone files, Cloudflare DNS exports and bulk DNS record text. The checker looks for A, AAAA, CNAME, MX, TXT, NS, SOA and CAA records plus common $ORIGIN and $TTL directives.

Does the DNS Zone File Checker test live DNS propagation?

No. Real-time DNS propagation checks, global node detection and DNS history lookup need multi-region servers, external datasets or ongoing crawling. This tool only checks pasted DNS text locally.

How strict are TXT, DMARC, DKIM and SPF checks?

The DNS Zone File Checker catches migration risks such as unquoted TXT values, duplicate SPF records, DMARC TXT records outside _dmarc and DKIM TXT records outside selector._domainkey. Provider-specific policy quality still needs manual review.

Why does the DNS Zone File Checker warn about trailing dots?

A missing trailing dot can make host targets relative to the zone origin during some imports. Relative names can be valid, but the warning helps you review MX, CNAME, NS and SOA targets before moving providers.

What should I do when the DNS Zone File Checker reports a failure?

Fix high-risk items first: invalid lines, CNAME conflicts, missing MX priority, duplicate SPF and wrong DMARC or DKIM hostnames. Then copy the suggestions, update the source records and rerun the local check.

Use the DNS Zone File Checker before a DNS migration

Run the DNS Zone File Checker before importing Cloudflare exports, changing nameservers or cleaning DNS records for a launch.

The check stays local in your browser and gives you grouped findings plus copyable repair suggestions.

Open DNS Zone File Checker Browse all tools

Local DNS zone file and record text checks only. No propagation check, global node test or DNS history lookup.