What to check after a DNS change

DNS changes need outside checks, timing notes, and one public page review before they are considered complete.

DNS work is easier to verify when the old value, new value, and check command are kept in the same note.

After the change

Check from a public resolver, not only the editing machine.
Confirm certificate coverage for the active name.
Open the public page that depends on the record.

Check from outside

The first DNS check should use a public resolver. Local caches and local network settings can make a change appear correct when it is not visible elsewhere.

Write down the resolver used for the check. This makes a later comparison easier if someone sees a different answer during the TTL window.

Review the dependent page

A DNS record is rarely the final goal. Usually it supports a page, a form, or a small public tool. After the record resolves, open the thing that depends on it.

This catches mismatches that a record check alone cannot see, such as a certificate that does not cover the name or a redirect that sends visitors to the wrong location.

Keep timing visible

DNS changes can create temporary uncertainty. The note should include when the change was made, the expected TTL behavior, and when the next check should happen if results are mixed.

This keeps the follow-up from becoming guesswork.

DNS review list

Record the old value and intended new value.
Check the record from one public resolver.
Confirm the active certificate covers the name.
Open the public page or path that uses the name.
Write the time of change and expected TTL behavior.