DNS records do not work as expected, dig shows two different SOAs
Usually means records sit with the registrar but NS records point to a different DNS platform. Both hosts claim authority, only one gets queried.
support/hosting-domeinen-dns/dns-soa-mismatch-registrar-hostingsteps: 5
Try this first
- Run dig SOA your-domain.com @1.1.1.1 and dig SOA your-domain.com @8.8.8.8. Different serial numbers or name servers back: a mismatch.
- Check WHOIS for the public NS records of your domain. Those are the servers the whole internet listens to.
- Compare with where you set records. Your A record at the registrar but NS at Cloudflare? Nobody listens to the registrar records, only to Cloudflare.
- Pick one DNS platform and put all records (A, MX, TXT, CAA, etc.) there. At the registrar leave only the NS delegation.
- Wait the TTL before migrating between platforms, or first lower TTL to 300 seconds and wait a day before the switch. Otherwise you see a mix of old and new across resolvers.
When to bring us in
Mismatch in production with mail impact (MX going to the wrong server, mail bouncing): during migration a second pair of eyes saves an hour of panic per hour of solo effort.
See also
- Domain expires tomorrow and nobody saw the emailAn expired domain doesn't transfer instantly. There's a redemption window, but you pay extra.
- Unsure whether to enable auto-renewDisabling auto-renew only makes sense for domains you'll truly drop. For anything live, just keep it on.
- New registrar asks for auth code, can't find itEPP code or transfer code is the password to move a domain from registrar A to B.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.