A DNS change is easier to manage when you know what should happen and how to undo it. Before editing anything, write down the hostname, record type, current value and intended new value.
Find the active DNS provider
The company where you bought the domain may not host its active DNS zone. Check the NS records and confirm that you are editing the authoritative provider. A correct record in an unused control panel will not affect the live domain.
Plan for old answers
If you control the record, lowering its TTL ahead of a planned move can reduce how long later answers are cached. It does not shorten the lifetime of an answer that a resolver already cached. Allow the old TTL to pass before relying on the lower value. Our TTL guide explains that timing.
Keep web and email settings separate
Moving a website does not always require moving email. Before changing nameservers, copy the records the new zone needs: web addresses, MX records, verification TXT records and email authentication policies. Keep a copy of the old zone so you can compare the two.
Check the exact name you changed
After saving, use DNS Lookup to inspect the record. Then compare public resolver answers in the propagation checker. Check both the root domain and www if your website uses both. Test the actual website and email service too; a correct DNS answer does not test the application behind it.
Keep the old service available during the move
Some visitors may still use cached answers. Where possible, keep both destinations working during that period. If results disagree, compare values and TTLs before repeatedly editing the zone. Repeated changes make it harder to tell which answer a resolver has cached.