Quick answer
Use the record type and destination supplied by the website host. An A record points to an IPv4 address, AAAA to an IPv6 address, and CNAME to another hostname. These records control a hostname, while nameservers control which provider answers the zone.
Before you start
Confirm the authoritative DNS provider and the host's exact instructions for the root domain and www or other subdomain. Preserve the old values and inspect existing records for conflicts.
What to do
- Identify the hostname being changed and whether the host supplied an IP address or a target hostname.
- Use the required record type and value at the authoritative DNS provider. Follow that provider's rules for root-domain aliasing rather than inventing an unsupported CNAME.
- Check for conflicting or stale A, AAAA, and CNAME records for the same name. Keep unrelated MX, TXT, and service records unchanged.
- Verify public DNS and then test the website over HTTPS, including both root and www when they are intended to work.
Check the result
Confirm that all published addresses lead to the intended service. A stale AAAA record can send IPv6 visitors somewhere different even when the A record is correct.
If something does not work
If the website still shows the old host, check caching, proxy status, redirects, and the host's domain mapping. Do not change nameservers unnecessarily for a simple website record update.
Related help
- Find where your domain's DNS is managed before changing records
- Plan DNS TTL changes before a website cutover
- Add a domain-verification TXT record without replacing existing records
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
