Problems DNS problem: NXDOMAIN looking up A

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:
sudo certbot --nginx -d -d
It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for and

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
  Type:   dns
  Detail: DNS problem: NXDOMAIN looking up A for - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version):
nginx version: nginx/1.24.0
The operating system my web server runs on is (include version):
ubunto 22.04
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot 1.21.0

Just like it says, there's no DNS record for You probably either want to:

  1. Set up that DNS record, and your server, so that users typing in that name with the www. on it will get to your site. At which point, you'll be able to get a certificate for that name. Or,
  2. Remove the -d from your request, if you don't need to support that www. name.

As confusing as it may be to some people, a domain name with www. on it and without are really two completely separate names as far as Internet infrastructure is concerned.


thanks I was setting up, I'll have my time to learn later about www. is best or what is the point to have it

1 Like