Custom domain not working (DNS_PROBE_FINISHED_NXDOMAIN)

Find your cause

6 causes, most likely first

1. 1

   The records are at the wrong provider

   How to tell: The domain's nameservers point somewhere else (Cloudflare, an old host, a site builder), so records added at the registrar are ignored.

   Fix

   Look up the nameservers on the domain's page at your registrar (or run dig NS example.com) and add the records at the provider they name.

2. 2

   The Name field has the whole domain

   How to tell: You typed www.example.com in the Name field, so the record became www.example.com.example.com.

   Fix

   Type only www. For the bare domain, use @ or leave it empty, depending on the registrar: our guides show which for each one.

3. 3

   It hasn't spread yet

   How to tell: You added or changed the records in the last hour.

   Fix

   New records usually work within minutes. Changed ones wait until the old answer expires, which can take hours. Your own computer may remember the old answer: try a phone on mobile data.

4. 4

   Only www, or only the bare domain, works

   How to tell: example.com opens but www.example.com doesn't, or the other way round.

   Fix

   They're two separate names. Add a record for each, or forward one to the other at the registrar.

5. 5

   The domain is on hold or expired

   How to tell: Nothing at the domain works, not even email, and the registrar shows it as expired or waiting for verification.

   Fix

   Renew it, or click the verification link registrars email for new domains and changed contact details: an unverified domain is suspended after about 15 days.

6. 6

   DNSSEC left over from a move

   How to tell: You changed nameservers and the domain stopped resolving entirely.

   Fix

   Turn DNSSEC off at the registrar, or add the new provider's DS record. Next time, switch it off before moving nameservers.

Questions

Also asked