Why DNS changes deserve attention

DNS records tell other systems where to send website visitors and email, and which services are associated with a domain. A mistaken or unauthorized edit can interrupt those services. For example, changing an A or AAAA record may send visitors to the wrong server, while changing an MX record may affect mail delivery. Changes to TXT records can alter email authentication or domain verification settings.

Not every unfamiliar change is malicious. A hosting move, an email-provider setup or an automated service can produce edits that someone on the team has not seen. The useful question is whether a change matches an approved task. A change log helps answer it by recording what changed and, where the provider supports it, who or what made the edit. Alerts make it more likely that someone notices promptly rather than discovering the change after a service stops working.

Build a baseline before you monitor

Start with a record of the DNS settings you expect to have. Include the domain or zone name, record type, host name, value, TTL and a short note describing the record’s purpose. Pay particular attention to records that direct web traffic or mail, such as A, AAAA, CNAME and MX records, along with TXT records used for SPF, DKIM, DMARC and service verification. Record the authoritative nameservers and the registrar account that controls them; a nameserver change can affect the entire zone even if individual records appear untouched.

Store the baseline somewhere accessible to the people responsible for the domain but not publicly exposed. Include a contact or change-request reference for each planned update. Do not put passwords, API tokens or private DKIM keys in this inventory. Review the baseline after approved changes so it remains useful: an outdated reference can make legitimate edits look suspicious and hide the importance of a later change.

Make logs and alerts actionable

If your DNS provider offers an audit log, check what it actually records. Useful details include the time, record name and type, old and new values, acting account or API credential identifier, and whether the action succeeded. Retention periods and available details vary by provider, so decide how your team will preserve the history it needs. A separate record of approved work, even a simple ticket or shared change calendar, gives you something to compare against the log.

Set alerts for changes that would matter most to your domain. Candidates include nameserver changes; new, deleted or edited web and mail records; and changes to email-authentication or verification TXT records. Where supported, also alert on DNS-management account activity, such as a new API credential or a change to multifactor authentication settings. Send alerts to a monitored destination that does not depend solely on the domain being monitored. Keep the message specific enough to identify the affected zone and record, but avoid sending sensitive account details through a broadly shared channel.

More alerts are not always better. If routine automation generates frequent notices, identify its expected account and scope rather than ignoring all alerts of that type. Test notifications with an approved, low-risk change and confirm that someone receives them, understands what to check and knows who to contact.

Investigate an unexpected edit

First, compare the alert with the provider’s change log and your record of approved work. Confirm the exact record, its previous and new values, the acting identity and the time. Ask the people or service owners who might have made the edit. If the log shows no matching change, check whether the alert came from a separate DNS monitor observing a different DNS response. Cached answers and differences between authoritative nameservers can complicate comparisons; they do not, by themselves, prove that someone edited the zone.

If the change is unauthorized or its origin remains unclear, preserve the log details and escalate to the person responsible for the domain. That person can check account access, active sessions and API credentials, then restore the approved configuration through the usual control panel or process. Avoid repeatedly changing records while investigating: overlapping edits make the timeline harder to follow. After a correction, verify the authoritative records and allow for caching before assuming every resolver will return the new answer.

Reduce the chance of a repeat

Monitoring works best alongside access controls. Give DNS editing rights only to accounts that need them, use multifactor authentication where available, and remove access that is no longer required. Keep automation credentials limited to the records or zones they must manage when the provider allows it. Require a second review for high-impact changes if your workflow supports one.

Revisit the baseline, alert rules and response contacts periodically. A new mail service or hosting provider may introduce legitimate records worth monitoring, while an old integration may leave access that can be removed. Logs and alerts cannot prevent every bad edit, but a clear baseline and a practiced review process make unexpected changes easier to recognize and address.

Back to category ↗