Start with the purpose and the correct zone

Before opening a DNS editor, write down what the change is meant to accomplish. “Connect the new help site” is more useful than “add a CNAME,” because it gives the reviewer a way to judge whether the proposed record fits the goal. Include the domain or subdomain affected, the service that requested the change, who owns that service, and how you will recognize success. If the request came from a setup screen, copy the required record details into your change note rather than relying on memory.

Confirm which DNS provider hosts the active zone. A domain can be registered in one place while its DNS records are managed elsewhere. Check the domain’s nameserver delegation and the zone you intend to edit before changing anything. If more than one team manages related domains, identify the person who can approve the change. This simple check helps prevent a well-documented edit from being made in a zone that visitors never use.

Record the before and after states

For each proposed edit, document the exact record name, type, value, and time to live (TTL). Record whether it is an addition, replacement, or deletion. Preserve the current value as well as the proposed one, including every existing record at the same name and type when relevant. DNS interfaces display names differently: one may show “www,” while another shows “www.example.com.” Note which form the editor expects so a reviewer can spot an accidental duplicate suffix.

A small change table or ticket can also capture the reason for each record. For example, a proposed CNAME for “help.example.com” might point to a provider-supplied hostname; the note should say which help site depends on it. Use illustrative or redacted values when sharing a change outside the authorized team. Do not put account passwords, private keys, or other credentials in a DNS change log. Some verification records contain tokens intended for DNS publication, but they should still be shared only with people who need to review them.

Review dependencies and unintended effects

Read the proposed change alongside existing records, not in isolation. Check whether the name already serves a website, redirects through a service, or appears in documentation used by another team. A CNAME generally cannot coexist with other record types at the same name; replacing an A or AAAA record with one may therefore require removing records that currently serve traffic. Changes to the zone apex may have different options in a provider’s interface. Review those options rather than assuming that a record suitable for a subdomain will work at the root domain.

Give email-related changes extra attention. An MX edit can affect where incoming mail is delivered, while changes to SPF, DKIM, or DMARC records can affect how mail is authenticated or handled. Confirm the complete intended set of records with the team responsible for email instead of adding a new value beside an old one without review. If a service asks for a record to prove domain control, check whether it must remain in place after setup. Also consider whether a planned nameserver change would replace the whole active zone, not just one record.

Agree on a publishing and rollback plan

Choose a time when the people who own the affected service can check it and respond if necessary. Your change note should identify who will publish, who will verify, and who can decide to roll back. Define the checks in advance: for a website, these might include looking up the hostname and loading the intended site; for mail, they might include confirming the expected MX records and testing delivery through the normal service workflow. A DNS lookup alone cannot prove that an application works.

Keep a copy of the prior record values and write down the steps needed to restore them. If the change replaces a record, specify which new value would be removed and which old value would return. A lower TTL set ahead of a planned migration may shorten the time some resolvers retain older answers, but it does not make every cache update immediately. Allow for cached results when setting expectations, and avoid promising an exact cutover time.

Publish, verify, and close the record

Immediately before publishing, compare the editor’s pending changes with the approved note. Check spelling, dots, record type, TTL, and whether the interface treats a value as a full domain name. Make only the reviewed edits; if a new requirement appears, pause and update the plan. After saving, confirm that the authoritative zone shows the intended records, then perform the service checks you agreed on. Results from other resolvers may differ for a while because they can retain earlier answers.

Finish the change log with the publication time, the person who made the edit, the checks performed, and the outcome. If something failed, record what was observed and whether you rolled back or made a separately reviewed correction. Keep the final record concise enough for the next domain administrator to understand what changed and why. That history turns a one-time edit into documentation the team can use during future migrations and troubleshooting.

Back to category ↗