Local before-and-after comparison · no DNS lookup
DNS cutover record comparison worksheet
Compare pasted current and proposed A, AAAA, CNAME, MX, NS, and TXT records, including entered TTLs and provider notes. Runs locally and makes no DNS requests.
Compare DNS values copied from the current and proposed zone before a cutover. This worksheet runs in your browser, sends no DNS queries, and does not publish changes.
Enter the current records
Use one tab-separated row per record: TYPE, NAME, VALUE, TTL seconds, PROVIDER NOTE. Use - for an unknown TTL and leave the final field empty when there is no note. Supported types are A, AAAA, CNAME, MX, NS, and TXT. Keep the record value as shown by your provider; separate multiple records into separate rows.
Enter the proposed records
Paste the current and proposed rows to review changes.
How to use the comparison
- Copy the current values, TTLs, and relevant provider settings from the authoritative DNS provider or zone export.
- Enter the planned values from the destination provider, preserving one record per row and any provider-specific notes you need to review.
- Review additions, removals, and metadata changes against your migration plan. Confirm the final values and proxy or routing settings in each provider before applying them.
The comparison treats record type and owner name without regard to letter case, removes a final dot from names, and compares values as entered after trimming outside whitespace. TXT values remain case-sensitive. It does not interpret provider-specific syntax, merge equivalent IP address spellings, validate a zone, or decide whether a change is safe.
Limits and sources
This is a text comparison of the rows you paste. It does not query authoritative servers or recursive resolvers, detect records you omitted, check DNSSEC, or establish propagation. TTLs and notes are displayed as supplied; confirm their meanings and current values with your providers.
- Cloudflare DNS record types describes common record types and their fields (checked November 4, 2026).
- RFC 1035, resource record format defines DNS resource-record fields including TTL (checked November 4, 2026).
Use the DNS record format checker for limited local A, AAAA, CNAME, and MX syntax checks, or the DNS TTL waiting-window estimator to model a cache interval from entered assumptions.
How it works
Paste current and proposed DNS rows using tab-separated type, owner name, value, TTL seconds, and optional provider note. The worksheet compares entered values and reports additions, removals, duplicate rows, and TTL or note changes. It does not query DNS or validate provider settings.
Good to know
Does this worksheet read my DNS zone or publish changes?
No. It compares only the text you paste in your browser. It does not contact a DNS provider, query resolvers, or change records.
Which record types can I compare?
The worksheet accepts A, AAAA, CNAME, MX, NS, and TXT rows. It compares their entered type, owner, and value text; it does not check whether the combination is valid for a particular provider.
Does a matching comparison mean the cutover is safe?
No. Verify the authoritative zone, TTL, proxy or routing settings, mail records, and provider-specific fields against your migration plan. The comparison cannot detect records or settings you did not enter.
Impact — TODO: apply/approval and configure referral URL — referral link not configured.
CJ Affiliate — TODO: apply/approval and configure referral URL — referral link not configured.
PartnerStack — TODO: apply/approval and configure referral URL — referral link not configured.