The site is down after a DNS change
A record was edited or deleted on the live zone, or the nameservers were switched to a provider that does not have the records yet.
Zone restored and verified
Working with DNS and domains?
A DNS change that looked harmless on the dashboard has taken the site or the mail offline, and the dashboard still says the records are correct. We find the record that is actually being served, work out what changed, and put it back on a footing you can touch again without holding your breath.
What it is
The Domain Name System translates names (example.com) to IP addresses so browsers, mail servers and APIs can reach each other. Records include A, AAAA, CNAME, MX, TXT, NS, SOA, SRV and CAA, each with its own job in the zone.
A domain is managed by a registrar for the name itself and by a DNS provider for the zone, which is often the same company but not always. SPF, DKIM, DMARC, and now DNSSEC and CAA all live as DNS records, so the same dashboard that points your website also decides whether your mail is trusted.
The honest version
No technology is all upside. This is where DNS and domains earns its place and where it tends to cause trouble.
Sound familiar?
The DNS and domains problems that bring people to us, and what you have once each one is fixed.
A record was edited or deleted on the live zone, or the nameservers were switched to a provider that does not have the records yet.
Zone restored and verified
The new host replaced the MX records with its own defaults, or the old MX was removed before the new mail service was ready to receive.
Mail flowing, SPF and DKIM aligned
Each SaaS that sends mail for you adds an include, and the ten-lookup limit is reached long before the list feels long.
SPF flattened and under the limit
DNSSEC was turned on at the DNS host but the DS record at the registrar does not match, so validating resolvers refuse every answer.
DS record matched or DNSSEC rolled back
The transfer code from the losing registrar is wrong, expired, or the domain is still inside a sixty-day lock window.
Domain at a registrar you trust
No DMARC record, a DMARC record that does not line up with SPF and DKIM, or a policy of none that nothing is acting on.
DMARC passing and reports monitored
A TTL that was set to a day or more before the change, or a resolver on the office network holding a stale answer.
Short TTLs before the next change
The registrar login is with a former developer and the billing card expired, which puts renewal and recovery at risk.
Ownership and billing in your name
What we do
Call us for one broken record, or hand us the whole zone.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Leave the zone alone and tell us what was changed and when. We check what the authoritative nameservers are actually serving, compare it to what the record should be, and put the correct value back. If the TTL was long we can often shorten the window by clearing specific resolver caches.
The honest answer is as long as the previous TTL was. If the old record had a TTL of one hour, most of the world sees the new value within an hour; if it was set to a day, parts of the internet can hold the old answer for a day. Setting the TTL low a few hours before a planned change makes the switch feel almost instant.
The new host usually overwrites MX and SPF with its own defaults during setup, which replaces the records that were routing mail. We put the correct MX back, line up SPF and DKIM with every service that sends for you, and confirm DMARC passes before calling it done.
Yes. We unlock the domain, get the transfer auth code, start the transfer at the new registrar and watch for the approval email. The zone itself can move at the same time or stay put, and we keep DNS serving throughout so nothing goes dark during the move.
SPF has a hard limit of ten DNS lookups per evaluation, and each include counts. Add a few SaaS senders and you quietly cross that line, which turns the record into a permerror and some receivers treat that as a fail. We flatten the record or move senders behind a single relay so you stay under the limit.
Estimates are free. Describe what is broken or what you want to change and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: