NS issues when renewing certificate

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:
thaumaturgic.dev

I ran this command:
certbot renew --dry-run

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/thaumaturgic.dev.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Attempting to parse the version 1.21.0 renewal configuration file found at /etc/letsencrypt/renewal/thaumaturgic.dev.conf with version 0.27.0 of Certbot. This might not work. Cert not due for renewal, but simulating renewal for dry run /etc/letsencrypt/options-ssl-nginx.conf has been manually modified; updated file saved to /usr/lib/python3/dist-packages/certbot_nginx/options-ssl-nginx.conf. We recommend updating /etc/letsencrypt/options-ssl-nginx.conf for security purposes. Plugins selected: Authenticator nginx, Installer nginx Renewing an existing certificate Performing the following challenges: http-01 challenge for thaumaturgic.dev Waiting for verification... Cleaning up challenges Attempting to renew cert (thaumaturgic.dev) from /etc/letsencrypt/renewal/thaumaturgic.dev.conf produced an unexpected error: Failed authorization procedure. thaumaturgic.dev (http-01): urn:ietf:params:acme:error:dns :: DNS problem: SERVFAIL looking up A for thaumaturgic.dev - the domain's nameservers may be malfunctioning. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/thaumaturgic.dev/fullchain.pem (failure) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ** DRY RUN: simulating 'certbot renew' close to cert expiry ** (The test certificates below have not been saved.) All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/thaumaturgic.dev/fullchain.pem (failure) ** DRY RUN: simulating 'certbot renew' close to cert expiry ** (The test certificates above have not been saved.) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1 renew failure(s), 0 parse failure(s) IMPORTANT NOTES: - The following errors were reported by the server: Domain: thaumaturgic.dev Type: None Detail: DNS problem: SERVFAIL looking up A for thaumaturgic.dev - the domain's nameservers may be malfunctioning

My web server is (include version):
nginx/1.14.0(ubuntu)

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

My hosting provider, if applicable, is:
digitalocean

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

DNS records seem correct anywhere I look for them other than from certbot. Note that the site will not resolve with http because .dev domains require https, but the site still resolves with http using the ip.

My name servers are all through digitalocean and have never "malfunctioned" like this before, but this has been an issue for at least a week now.

DNSSEC is broken: thaumaturgic.dev | DNSViz.

Where there should have been a DNSKEY resource record in your zonefile, it's missing. Maybe you deleted it?

3 Likes

I deleted a bunch of DNS records after shutting down a mail server on the domain and may have deleted that by accident. I'll look into it and update you. Thanks!

I've disabled DNSSEC in my domain provider (I'd only ever enabled it for the sake of the mail server anyway), but I still get the same output

EDIT: Nevermind! It just hadn't propagated yet. That fixed it. Thanks a lot!

3 Likes

Glad you got the certificate issuance fixed. Although it would be better for the entire DNS ecosystem to properly enable DNSSEC of course :wink:

2 Likes

And...
Welcome to the LE community forum @Thaumaturgic :slight_smile:

1 Like

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