Certbot NGINX, DNS problem: NXDOMAIN looking up A

Help
1

Fail in a domain and subdomain that is working online (!). How to say to certbot that it is valid? No problem with IP or A names, or CNAMEs, no problem with NGINX scripts.

tls-sni-01 challenge for www....
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. xpto.myDomain1 (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for xpto.myDomain1, abcd.myDomain1 (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for abcd.myDomain1, xyz.myDomain1 (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for xyz.myDomain1, .....

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

   Domain: xpto.myDomain1
   Type:   connection
   Detail: DNS problem: NXDOMAIN looking up A for xpto.myDomain1

   Domain: abcd.myDomain1
   Type:   connection
   Detail: DNS problem: NXDOMAIN looking up A for abcd.myDomain1

   Domain: xyz.myDomain1
   Type:   connection
   Detail: DNS problem: NXDOMAIN looking up A for xyz.myDomain1

   Domain: ....

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A record(s) for that domain
   contain(s) the right IP address. Additionally, please check that
   your computer has a publicly routable IP address and that no
   firewalls are preventing the server from communicating with the
   client. If you're using the webroot plugin, you should also verify
   that you are serving files from the webroot path you provided.
2

Hi @ppKrauss,

It won't be possible to help you without knowing the domain names that are failing. Can you share those?

3

Sorry @cpu, was my mistake, was new names with no CNAMEs… As soon as I registered the CNAMES in the domain, the certbot certificate was produced.

PS: delete the question?

4

Hi @ppKrauss,

Glad you got it sorted out!

I'd prefer not to delete the question since it might be helpful to someone in the future :slight_smile:

5

Thanks @cpu. Perhaps need an issue ticket, “NXDOMAIN looking up A” is a wrong message, “NXDOMAIN looking up A or CNAME” is better. The solution in trivial case as mine is

  • add new (need for) CNAME or
  • delete the (expurious) Nginx server-rules for that non-existent server-name.
6

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