Error while attempting to generate certificate: NXDOMAIN looking up A for


#1

Hi guys,

I’m getting the following message while attempting to generate a certificate for my nginx reverse proxy.

vinod@nginxproxy:~$ sudo certbot --nginx
[sudo] password for vinod:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
No names were found in your configuration files. Please enter in your domain
name(s) (comma and/or space separated) (Enter ‘c’ to cancel): domain1.com
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for domain1.com
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. domain1.com (http-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for domain1.com

IMPORTANT NOTES:
-The following errors were reported by the server:

Domain: domain1.com
Type: None
Detail: DNS problem: NXDOMAIN looking up A for domain1.com

Im quite a newbie with certbot, can anyone point in the right direction?


#2

What’s your domain? Apparently it isn’t registered, or doesn’t have any DNS records.

Or, if the request was for a subdomain, maybe that didn’t exist.


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. https://crt.sh/?q=example.com), 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:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

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):


#3

This is a bit concerning:

Are you familiar with NGINX?


#4

Found out that the issue was due to my domain being not registered. Thanks for pointing that one out.

Guess there still some work to be done before i can generate the certs.


#5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.