Working with DNS and domains?

Site or email down after a DNS change? We fix it.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

dns.log

still failing

What it is

DNS and domains at a glance

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.

Type
Internet naming and routing
First specified
RFC 1034 and 1035, 1987
License
Open standard
Maintained by
IETF plus every registrar and DNS host
Typically used for
Hosting websites, routing email, SaaS verification, failover, geographic load balancing

The honest version

DNS and domains pros and cons

No technology is all upside. This is where DNS and domains earns its place and where it tends to cause trouble.

Where DNS and domains is strong

  • Cheap or free to runZones are usually included with the registrar or with a provider such as Cloudflare at no extra cost, which keeps the running bill close to zero.
  • Instant to clickA, CNAME, MX and TXT records are a few fields in a dashboard, so most routine changes are the work of a minute once you know what to type.
  • Splits traffic the way you wantWeighted and geographic answers let you send some visitors to one backend and the rest to another, which is useful for load balancing and rollouts.
  • Quick failoverDNS-level health checks can swing traffic to a standby server in seconds, which is a cheap substitute for a full high-availability setup.
  • Modern dashboards and low TTLsProviders such as Cloudflare and Route 53 give near-zero TTLs, audit logs and clear dashboards, so changes land fast and can be traced later.

Where DNS and domains bites

  • TTLs mean changes take timeResolvers cache answers for the TTL you set, so a record change rolls out gradually rather than everywhere at once.
  • Moving registrars is slowTransfers need the right auth code and are blocked for sixty days after registration or a previous transfer, which catches people out at renewal time.
  • The email chain is fragileSPF, DKIM and DMARC lean on each other, so adding another sending service often breaks a record that looked fine the day before.
  • DNSSEC can take you offlineA mismatched DS record or an expired signature makes every validating resolver return SERVFAIL, which looks exactly like the domain has vanished.
  • Apex CNAME is not allowedA plain CNAME at the root of the domain breaks the standard, so hosts that only give you a hostname need ALIAS, ANAME or a proxied record.
  • Losing the registrar account is near-fatalIf the login and the recovery email are both gone, getting the domain back can take weeks of paperwork, and sometimes does not work at all.

Sound familiar?

Common DNS and domains problems we fix

The DNS and domains problems that bring people to us, and what you have once each one is fixed.

DNS_PROBE_FINISHED_NXDOMAIN

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

MX record missing: mail bouncing

Email stopped after we moved hosts

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

SPF permerror: >10 lookups

SPF keeps failing on new senders

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 validation failed

The domain returns SERVFAIL everywhere

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

transfer rejected: wrong auth code

The move to a better registrar is stuck

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 record at _dmarc

Mail is going to spam

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

propagating: up to 48h

Changes are not showing up

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

admin contact: unknown

Nobody knows where the domain lives

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

DNS and domain help, from rescue to upkeep

Call us for one broken record, or hand us the whole zone.

Rescue
Site or mail down after a change. We get traffic flowing again first, then work out exactly what the edit broke.
Email records
SPF, DKIM and DMARC set up so each sending service is authorised and the inbox providers trust the mail.
Registrar moves
Transferring domains to a registrar you actually control, with auth codes, locks and contacts handled in order.
DNSSEC and CAA
Turning on signing without taking the domain offline, and locking down which certificate authorities can issue for you.
Migrations
Moving zones between providers with low TTLs, parallel serving and a backout plan if anything misbehaves.
Managed Tech
Monitoring records, renewals and certificates, with a team to call when something needs to change.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running DNS and domains alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

DNS and domains questions

Something else? Call+1 737 727 7327

My website is down after a DNS change, what do I do?

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.

How long does DNS propagation actually take?

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.

Why is our email suddenly bouncing after we moved hosts?

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.

Can you move our domain from GoDaddy to a better registrar?

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.

Why does SPF keep failing when we added another email service?

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.

How much does DNS and domain help cost?

Estimates are free. Describe what is broken or what you want to change and you get a price before any work starts.

Free estimate

Domain or DNS giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.