DNS change · Silent redirect risk

What happens when someone changes my DNS?

A DNS change can redirect your website, break email, or point visitors at a lookalike without transferring the domain at all. If nobody is watching the baseline, you learn from customers, not from a dashboard.

Blast radius of a “small” DNS edit

Records look technical. Outcomes feel commercial.

  • Nameserver changes move the authority for the zone.
  • After TTL fades, the internet asks a different set of hosts for your answers.
  • A malicious actor with registrar or DNS panel access can swap NS, alter A/AAAA, or rewrite MX.
  • A well-meaning contractor can do the same by “cleaning up” records during a migration.
  • Outcomes operators see: site redirects to unexpected content, SSL mismatches, mail bouncing, analytics falling off a cliff, and ads still spending against a broken destination.
Web Wrong A/AAAA or CNAME
Mail MX or auth records drift
NS Whole zone leaves your set
TTL Damage spreads on cache expiry

Detection vs prevention

Locks help. They do not narrate every DNS edit.

Access hygienePrevent

Registrar 2FA, least-privilege DNS users, and change discipline reduce accidental and hostile edits.

Aepto baselineDetect

Theft Guard and DNS monitoring raise Attention when live signals leave the learned baseline for that name.

Named Attention items

Know which domain drifted. Do not dig through five registrar UIs after a vague “DNS might be wrong” Slack.

History for triage

When you call the registrar or DNS host, timestamps beat memory. History supports the “when did this start?” question.

Team channels (paid)

Webhooks push drift into Slack, Discord, Teams, or HTTP when email to one inbox is not enough.

Pair DNS watch with uptime and content

DNS drift and downtime often arrive together. A hijack that redirects traffic may still “respond” from the attacker’s host. Uptime alone can look odd or even green depending on what you probe. Content Monitoring (paid) helps when the wrong page still returns 200.

Aepto does not edit your DNS zone for you and does not replace registrar locks. Alerts and history are what Aepto provides.

DNS and Theft Guard monitoring in Aepto

Which DNS change breaks what?

Records look technical. The damage is commercial.

DNS record changes and their impact
Record changedWhat breaksWho notices first
Nameservers (NS)Everything: the whole zone is answered by someone elseCustomers, as caches expire
A, AAAA or CNAMEThe website goes to the wrong serverVisitors and paid ad clicks
MXInbound mail bounces or is interceptedSales and support, hours later
SPF, DKIM or DMARC (TXT)Outbound mail lands in spam or is rejectedMarketing, from falling open rates
CAACertificates fail to renew, or any CA can issue oneOps, at the next renewal

What happens in the hours after a hostile nameserver change?

The damage spreads as caches expire, which is why early reports look random.

  1. Minute 0
    Nameservers change at the registrar

    Nothing looks different yet. Resolvers still hold cached answers.

  2. Within the TTL
    Caches expire unevenly

    Some visitors and mail servers see the new zone, others the old one. TTLs are often between 5 minutes and 24 hours.

  3. Hours
    Web and mail follow the new zone

    Pages, logins and mail go wherever the new nameservers point.

  4. Next check
    Aepto flags the drift

    The change appears in Requires Your Attention with old and new values and a timestamp.

  5. Response
    You revert at the registrar or DNS host

    Aepto keeps the history. The fix happens at your provider.

How do you control DNS changes without slowing deploys?

Speed for launches, brakes for accidents.

  • Give contractors temporary, least-privilege DNS access instead of permanent admin.
  • Write down the expected nameservers for every production domain.
  • Announce migration windows, then update the Theft Guard baseline when they finish.
  • Treat MX and SPF/DKIM/DMARC changes as seriously as A records.
  • Check resolution from two networks before you revert.
  • Outside a planned window, treat a nameserver change as a compromise until proven otherwise.

Why do DNS changes do damage so quietly?

Three facts that explain the delay and the blast radius.

TTL

how long resolvers may cache a record before asking again, which is why bad changes spread gradually

Source: RFC 1035

clientTransferProhibited

is the status code behind the usual "registrar lock". It blocks transfers, not DNS edits

Source: ICANN

5,000 a day

senders above this to Gmail must have SPF, DKIM and DMARC in place (since February 2024)

Source: Google Workspace Admin Help

Common questions

Can DNS change without a domain transfer?

Yes. Nameserver or record changes can redirect web and mail while the name still shows as yours at the registrar. That is why drift detection matters even when locks are on.

What does Aepto alert on?

Theft Guard and DNS monitoring compare live signals to a learned baseline for names in your inventory. Unexpected NS or registrar moves surface in Requires Your Attention.

Will Aepto undo a bad DNS edit?

No. Aepto alerts and preserves history. You (or your DNS host) revert records. Monitoring is detection, not remote DNS admin.

How does this relate to email?

MX and related records moving with a malicious or mistaken change can kill deliverability overnight. Catching NS drift early often limits that blast radius.

Is this the same as Domain Watch?

No. Domain Watch is for names you do not own yet. DNS and Theft Guard cover domains already in your portfolio.

Why is a silent DNS change dangerous?

Traffic, email, and APIs can be rerouted while the domain still "resolves." Visitors may see phishing or blank pages; mail can vanish; SEO trust erodes, often without a classic downtime alarm.

How does Aepto detect DNS drift?

Aepto learns a DNS baseline and surfaces unexpected changes in Attention alongside uptime and renewals, so drift is not only a ignored registrar email.

Do not learn about DNS changes from customers.

Import domains free. Put baseline drift in the same queue as uptime.

Aepto Theft Guard showing nameserver and registrar baseline alerts