Practical domain guide
How to point a domain at a website
Pointing a domain means changing DNS records so browsers can find the server that hosts your site. The domain stays registered in the same account. You are changing directions, not transferring ownership.
Before changing anything
Copy or export the current DNS records. Identify where DNS is actually managed; it may be the registrar, Cloudflare or another provider named by the domain’s nameservers. Do not delete MX records used for email. Find the exact target your hosting service supplies and lower the TTL in advance if you are planning a timed move.
The common record pattern
The root domain is usually shown as @. If your provider supports an ALIAS, ANAME or flattened CNAME at the root, point it to the supplied hostname. Otherwise add the supplied A record for IPv4 and AAAA record for IPv6. Point www with a CNAME, either to the hosting target or to the root domain. Avoid leaving old A or AAAA records that send some visitors elsewhere.
Porkbun
Open Domain Management, expand the domain and open DNS Records. Add an ALIAS record for the root when the host gives you a target hostname, or add its A/AAAA values. Add a CNAME for www. Porkbun normally uses a blank host or @ for the root; check the label shown in its form.
Namecheap
Open Domain List → Manage → Advanced DNS. Use an ALIAS Record for @ when appropriate, or A/AAAA records from the host. Add a CNAME Record with host www. Remove the parking records if they conflict.
Cloudflare
Open the zone and choose DNS → Records. Cloudflare flattens a CNAME at the root. While diagnosing a new connection, set the record to DNS only so the hosting service sees the real answer; enable the orange-cloud proxy later only if the host supports it.
GoDaddy
Open the domain’s DNS management page. GoDaddy commonly expects A/AAAA records at @ because it does not offer a general external apex CNAME. Add www as a CNAME. Its forwarding feature is different from DNS hosting and is not a substitute when the host asks for records.
Route 53
Open the correct hosted zone. A Route 53 Alias can target selected AWS resources, not any arbitrary hostname. For an external hosting service, use its A/AAAA values at the apex and a normal CNAME for www. Check that the domain’s nameservers match this hosted zone.
Verify safely
Use the host’s verification button and query both the root and www names. DNS propagation is caching, not a file copied around the world: different resolvers can show different answers until earlier TTLs expire. Once routing is correct, certificate issuance can still take a few minutes.