DNS problem: NXDOMAIN looking up A for

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: declaracionpatrimonial.gob.mx

I ran this command: sudo certbot --nginx

It produced this output: Failed authorization procedure. declaracionpatrimonial.gob.mx (http-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up A for declaracionpatrimonial.gob.mx - check that a DNS record exists for this domain

My web server is (include version): nginx 1.14

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

My hosting provider, if applicable, is: NA

I can login to a root shell on my machine (yes or no, or I don’t know): Yes

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

1 Like

Hi @abelhOrihuela

did you change something in the last three hours? Checking your domain there is no problem visible.

Not with https://check-your-website.server-daten.de/?q=declaracionpatrimonial.gob.mx

Host T IP-Address is auth. ∑ Queries ∑ Timeout
declaracionpatrimonial.gob.mx A 167.172.220.80 Santa Clara/California/United States (US) - DigitalOcean, LLC No Hostname found yes 1 0
AAAA yes
www.declaracionpatrimonial.gob.mx Name Error yes 1 0

You have a valid DNSSEC. Rechecked with Unboundtest - https://unboundtest.com/m/A/declaracionpatrimonial.gob.mx/2J2YGLIF - no problem:

Feb 11 08:27:49 unbound[16787:0] info: validate(positive): sec_status_secure
Feb 11 08:27:49 unbound[16787:0] info: validation success declaracionpatrimonial.gob.mx. A IN

and with DNSSEC Analyzer - declaracionpatrimonial.gob.mx - all is green.

1 Like

They use the servicios-nic.com.mx nameservers which have problems with IPv6.

I would expect you to get "SERVFAIL" or "query timed out" errors from Let's Encrypt. "NXDOMAIN" seems strange.

2 Likes

Now I have this problem, how to solve this issue I don’t have much experience with DNS

1 Like

Thanks for you answer, now I have other problem

DNS problem: query timed out looking up A for declaracionpatrimonial.gob.mx

1 Like

The servicios-nic.com.mx nameservers do not seem to work with Let’s Encrypt.

I’m not sure why. The nameservers have broken IPv6 connectivity, but that should not cause Let’s Encrypt to always fail.

You can maybe try to figure out and fix what’s wrong, or move your domain to a different DNS service.

2 Likes

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