How to Request a Domain or DNS Change Safely
How to Request a Domain or DNS Change Safely
DNS connects a hostname, such as www.example.com, to websites, email, verification services, and other systems. A small record change can interrupt the site or mail for everyone, so domain and DNS requests require exact values, clear authorization, and a rollback plan. Never send registrar or DNS passwords by email or support ticket.
Information to include
Provide one line per requested record with:
- the domain and exact hostname (
@,www,portal, and so on); - record type (
A,AAAA,CNAME,TXT,MX,SRV, orCAA); - current value, if known;
- requested new value, copied from the receiving provider;
- TTL requested, or “leave unchanged”;
- Cloudflare proxy status for eligible
A,AAAA, orCNAMErecords; - purpose of the change;
- required date/time and time zone;
- who approved it; and
- a vendor documentation link or verification instructions.
Cloudflare’s official record-management guide confirms that record fields vary by type and highlights proxy status and TTL as particularly important settings.[1] A screenshot alone is not enough; text values reduce transcription errors.
Registrar, nameserver, and DNS-record changes are different
The registrar is where the domain is registered. Nameservers delegate DNS authority. Individual DNS records live with the active DNS provider. Changing an A record is not the same as changing nameservers, and transferring a registrar is a separate process again. If you are unsure which change the vendor requires, ask the vendor to identify it in writing before anyone edits production DNS.
Nameserver changes can affect every service under the domain if the destination zone is incomplete. Before such a change, an administrator should compare the complete current zone, including website, email, verification, and security records, with the destination.
Plan around TTL and caching
TTL controls how long resolvers cache a DNS record. Cloudflare explains that longer TTLs can improve lookup efficiency but also make updates take longer to reach users.[2] Cloudflare proxied records use an automatic TTL of 300 seconds, while local caches can make the visible change take longer. Do not promise an exact worldwide propagation time.
Lowering a TTL shortly before a change does not instantly expire copies already cached under the old TTL. A planned migration should set an appropriate TTL far enough in advance, then restore the normal value after validation. The DNS administrator, not the requester, should decide whether that is appropriate.
Safe change process
- Verify that the requester is authorized for the domain.
- Export or screenshot the current zone and record the old value.
- Check for conflicts, such as an existing record with the same name or a
CNAMEwhere another record type is required. - Confirm dependent services, especially MX, SPF, DKIM, DMARC, verification TXT records, and subdomains.
- Make only the approved change. Cloudflare’s dashboard flow is DNS Records → Add record or Edit → Save.[1]
- Validate from more than one resolver or network after the expected cache window. Test the exact hostname and the service it supports.
- Keep the former value and rollback criteria until the change is confirmed.
Do not delete unfamiliar records, combine multiple TXT values, change nameservers, disable DNSSEC, or switch Cloudflare proxy status merely to “see if it works.” Those actions can affect unrelated services or security.
After the change
Website validation should include HTTP and HTTPS, the apex domain, www, and required subdomains. Email-related changes should be validated through the email provider’s official tools; do not test by altering other mail records. A vendor-verification record may take time to be recognized even after public DNS answers correctly.
If the result is wrong, send support the requested record, the old and new values, change time and time zone, screenshots or query results, affected locations, and exact error. Do not repeatedly edit the record during propagation, because that creates overlapping cached answers and makes diagnosis harder.