When something isn’t resolving correctly — email not arriving, a subdomain not loading, a service integration failing — and you don’t know which specific DNS record is actually wrong, this audits your full DNS zone to find the actual discrepancy, distinct from making a change you’ve already identified you need.
Note exactly what’s failing before ordering a broad audit
Being specific about the actual symptom (“email isn’t arriving,” “this subdomain shows a 404,” “this service says my domain isn’t verified”) gives us a much faster, more targeted starting point than a general “something with DNS seems wrong,” even though this fix ultimately reviews your full zone.
DNS record audit & correction
A DNS discrepancy found by auditing the full zone when you don't know which record is wrong.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Something isn’t working correctly and you suspect a DNS record is wrong, but don’t know which one | This fix covers it |
| You already know exactly which DNS record needs changing | DNS zone record management at host, or Registrar-level DNS & nameserver changes, the direct, targeted fix instead |
| You want DNS migrated to Cloudflare specifically, not audited in its current location | Cloudflare DNS migration from registrar |
| The issue is specifically mail routing through Google Workspace | Google Workspace mail routing for domain, the more specific, guided version if that’s your actual situation |
What you are seeing
- A specific service or function failing in a way that suggests a DNS misconfiguration
- Uncertainty about which of many DNS records is actually the problem
- The issue possibly following a past migration, hosting change, or DNS provider switch
- Inconsistent behaviour that might point to a propagation issue rather than a genuinely wrong record
Common causes
- A record left over from a previous configuration, now conflicting with current, correct records
- A record with an incorrect value, introduced by a past manual edit or migration error
- A missing record that should exist for a specific service (a verification TXT record, an MX entry) to function
- Conflicting records for the same purpose, with an outdated one taking precedence over the intended, current one
- Two DNS providers both technically authoritative after an incomplete migration, returning inconsistent answers depending on which one actually gets queried
What we do
- Review the full DNS zone comprehensively
- Cross-reference records against what each connected service actually expects
- Identify the specific discrepancy causing the reported symptom
- Correct the identified record
- Verify the specific, originally reported issue is now resolved
- Provide a written summary of what was found and corrected, and flag anything else notable found along the way
What is included
- A comprehensive DNS zone review
- The specific discrepancy causing the reported issue identified and corrected
- Verified resolution of the original symptom
- A written summary of findings and corrections, including anything else notable found
Not included
- Making a specific, already-identified DNS change — a more direct, targeted fix instead if you already know what’s needed
- DNS migration to a different provider, a separate, related fix
- Resolving an issue that turns out to be unrelated to DNS entirely, once that’s determined
- Ongoing DNS monitoring as a standing service
Questions about this fix
Why would I need a full audit instead of just telling you what to fix?
If you already know the specific change needed, a direct, targeted fix is faster and more appropriate — this audit is specifically for when something's wrong but the exact DNS cause isn't yet known, which needs a broader review to actually find.
How would old, leftover DNS records cause a current problem?
An outdated record can sometimes take precedence over a newer, correct one, or simply create confusion when troubleshooting, since having conflicting information about the same thing makes it harder for services to know which is authoritative.
Will this audit find issues beyond the one I originally reported?
Often, yes — a comprehensive review sometimes surfaces other discrepancies along the way, which we'd flag in the report even if they're not causing an active problem yet.
How long does a DNS audit like this typically take?
The review itself is usually quick, though confirming a fix has actually resolved the original issue can take longer if DNS propagation delay is involved.
What if the audit finds that DNS isn't actually the cause of my problem?
We'd tell you that plainly, since a thorough DNS review that finds everything correctly configured is still a useful, if not the hoped-for, outcome — it means the actual cause lies elsewhere, which is valuable to know before spending more time looking at DNS.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.