Identify who manages the zone
Nameservers identify the provider managing your DNS zone. First check whether this is your registrar, host or a separate DNS service. Changing nameservers does not copy existing records: prepare the new zone before changing delegation.
Common records and their purpose
An A record maps a name to an IPv4 address; AAAA maps it to IPv6. CNAME maps a name to another name. MX identifies mail servers, while TXT publishes verification values and other policies. Use the exact destinations and priorities supplied by each service provider, rather than example addresses from a tutorial.
Preserve website, email and verification records
Record or export the current zone before editing it. Review the root domain, www, active subdomains, MX and email or verification TXT records. Changing only the website destination normally does not require changing email records. Do not delete an entire zone to fix one record.
Check the result at several levels
After saving, query authoritative nameservers and test from another connection. Cached values can remain visible depending on their TTL and resolver. Check DNS resolution, HTTPS certificates and website responses separately: one working component does not prove that the others work.
Keep a rollback plan
Document previous values and retain access to the old provider while verifying changes. If you use DNSSEC, review delegation and related records to avoid validation errors. Share the plan with whoever manages the website and email before carrying it out.
Technical reference: DNS record types, Cloudflare documentation.