Certbot: Detail: DNS problem: NXDOMAIN looking up A for www.example.com - check that a DNS record exists for this domain
Let's Encrypt could not resolve the domain you asked a certificate for; no A/AAAA record exists.
DNS problem: NXDOMAIN looking up A forDNS problem: NXDOMAIN looking up A for www.example.com - check that a DNS record exists for this domainDNS problem: SERVFAIL looking up CAADNS problem: looking up A for example.com: DNSSEC: DNSKEY MissingDetail: DNS problem: NXDOMAIN Meaning
Every name in -d must resolve publicly to your server for HTTP-01 validation. Add the missing record, or remove that name from the request. Wait for DNS propagation and verify with dig. Also check for AAAA records pointing to an IPv6 address where the server isn't listening.
Common causes
- No DNS record for the requested subdomain (often
www) - Domain not delegated or DNS not yet propagated
- Typo in the domain
- AAAA record pointing to a wrong IPv6 address
- Using the domain before registering/pointing it
⚡ Quick fix
- Create A/AAAA (or CNAME) records for each name
- Verify:
dig +short A www.example.com - Remove names that don't need a certificate
Detailed fix by platform
Linux
dig +short A www.example.com; dig +short AAAA www.example.com
How to diagnose
- Record — Exists for each -d?
- Propagation — Resolved publicly?
- IPv6 — AAAA correct?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SSL / TLS
- NET::ERR_CERT_COMMON_NAME_INVALID NET::ERR_CERT_COMMON_NAME_INVALID: Your connection is not private (certificate is for a different domain)
- no start line OpenSSL: unable to load certificate / PEM routines:get_name:no start line (key values mismatch)
- NSURLErrorServerCertificateUntrusted (-1202) iOS: Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be 'example.com'"
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026