NXDOMAIN error using certbot

Help
1

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. crt.sh | 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: hub.raimax.com.br

I ran this command:certbot --nginx

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx

Which names would you like to activate HTTPS for?

1: hub.raimax.com.br

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1
Requesting a certificate for hub.raimax.com.br
Performing the following challenges:
http-01 challenge for hub.raimax.com.br
Waiting for verification...
Challenge failed for domain hub.raimax.com.br
http-01 challenge for hub.raimax.com.br
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: hub.raimax.com.br
    Type: dns
    Detail: DNS problem: NXDOMAIN looking up A for hub.raimax.com.br -
    check that a DNS record exists for this domain; DNS problem:
    NXDOMAIN looking up AAAA for hub.raimax.com.br - check that a DNS
    record exists for this domain

My web server is (include version): nginx/1.18.0

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

Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 1.12.0

2

Welcome @viniciusbortolo

Your newns2 DNS name server does not respond with the correct A record. Your newns1 is correct just not newns2

# Note NXDOMAIN 
dig A hub.raimax.com.br @newns2.raimax.com.br.
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44509
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

# Got proper A record 
dig +noall +answer A hub.raimax.com.br @newns1.raimax.com.br.
hub.raimax.com.br.      3600    IN      A       186.233.176.54
5 Likes
3

After you get that sorted out, you might want to look into updating certbot OR using another ACME client.

4 Likes