Compare DNS records: old host vs new host
Compare your domain’s records on the old host and the new host side by side, and catch a missing MX or TXT record before you switch nameservers.
What this tool checks
DNSPeek asks both sides for the A, AAAA, CNAME, MX, TXT, NS and CAA records of the name you enter. A nameserver is asked without recursion, so it answers from the zone it hosts; public DNS is asked through public resolvers. Only records that belong to the name itself are compared, so an alias shows up as its CNAME record.
How to read the result
Each record type is marked Same, Different, Same pool (rotating), Missing on new, Only on new, or None on either. “Missing on new” is the one to fix before the switch. A and AAAA are asked three times per side, so a round-robin pool shows as one rotating set rather than a difference. Different A or AAAA records are expected when the site moves to a new server; then use the preview link the result offers to see the site on that IP.
What to check after a migration
Run the comparison for the bare domain and for www and any subdomains you use (shop, mail, autodiscover). After the switch, check that the registry delegates to the new servers with the nameserver checker and that mail still works with the MX lookup. The migration playbook has the full list.
Frequently asked questions
When should I compare DNS between two nameservers?
Before you point your domain at a new DNS host. The new host’s nameservers already answer for your zone, so you can check that every record, especially MX and TXT for email and verification, exists there before visitors and mail servers start asking.
What does “public” mean as the old side?
It asks public resolvers, so you see what visitors get today, whichever nameserver they reach. Enter the old host’s nameserver instead to compare the two zones directly, without caches.
Why does the new nameserver refuse or show no answer?
It does not host your zone yet, or the zone was added under a different name. Create the zone at the new DNS host first; most hosts show the nameserver names in the DNS settings of your domain.
Is a different A record a problem?
Not when the site is moving: the new zone should point to the new server. Differences in MX or TXT deserve a closer look, because a missing MX stops email and a missing TXT can break SPF or a domain verification.
Can I enter an IP address instead of a nameserver name?
Yes, a public IP address of the nameserver works. Private, reserved and DNSPeek addresses are refused, and only DNS questions are sent.
Moving a site to a new server?
See the site on the new server before you change DNS: DNSPeek gives you one HTTPS preview link that works on any device and that you can share with your team or client. No hosts file, no VPN.
Create a free preview link