Connect a domain from GoDaddy
Updated
GoDaddy's DNS has no ALIAS record (also called ANAME or CNAME flattening), so it can't point a bare domain like example.com at your site. A subdomain such as shop.example.com works on GoDaddy as it is. For a bare domain, keep the domain registered at GoDaddy and let Cloudflare (free) answer for its DNS instead. It takes about 20 minutes of work, then some waiting.
The same steps work for any registrar without ALIAS: only where you change the nameservers (step 4) differs.
A subdomain: add one record at GoDaddy
- In GoDaddy, open My Products, then your domain's DNS.
- Click Add New Record, choose CNAME, and in Name type the part before your domain (for
shop.example.com,shop). - In Value, paste the value the dashboard shows, and save.
That's all: the dashboard finds it on its own.
A bare domain: move the DNS to Cloudflare
1. Note your email records
Your email (Microsoft 365, Google Workspace, GoDaddy's own email…) depends on DNS records called MX and TXT. In GoDaddy's DNS page, take a screenshot of all your records before you start, so you can check none go missing.
2. Add the domain to Cloudflare
- Create a free account at cloudflare.com.
- Choose Add a domain, enter your domain, and pick the Free plan.
- Cloudflare copies your existing records. Compare them with your screenshot, and add any that are missing, above all every MX and TXT record. Otherwise your email stops when you switch.
3. Turn off DNSSEC at GoDaddy (if it's on)
In GoDaddy's DNS settings, look for DNSSEC. If it's on, turn it off first: with it on, the domain stops working when the nameservers change.
4. Change the nameservers at GoDaddy
- Cloudflare shows two nameservers, like
ada.ns.cloudflare.comandbob.ns.cloudflare.com. - In GoDaddy, open your domain's DNS page, then Nameservers → Change nameservers.
- Choose I'll use my own nameservers (it may say Enter my own nameservers), enter Cloudflare's two, and remove any others.
- Save, and confirm the warning: it's expected, since Cloudflare holds your records now.
Back in Cloudflare, click Check nameservers. The switch usually completes within an hour, and at most a day. Cloudflare emails you when your domain is active.
5. Add the site's records in Cloudflare
In the dashboard, go to Site → Domains and connect the domain to see its three records. In Cloudflare, under DNS → Records, add each of them:
- ALIAS record: in Cloudflare, add it as a CNAME with Name
@. Cloudflare flattens it for you. Delete any A or AAAA records named@first. - CNAME record: Name
www. Delete any oldwwwrecord first. - TXT record: Name
_cf-challenge, with the value exactly as shown.
Set both CNAME records to DNS only (grey cloud), not Proxied (orange cloud). Your site already has its own HTTPS and CDN.
6. Wait for it to connect
The dashboard checks each record and marks it Found. Once all three are found, the HTTPS certificate is issued and your site goes live on your domain, usually within minutes.
It isn't connecting
- A record shows Wrong and mentions Cloudflare's proxy: set that record to DNS only (grey cloud).
- The bare domain shows Wrong with other addresses: delete the old A records named
@(often GoDaddy's parking page) in Cloudflare. - Nothing is found after a day: check in Cloudflare that the domain says Active. If it doesn't, check the nameservers at GoDaddy.
- Email stopped: add the missing MX and TXT records from your screenshot in Cloudflare.