DNSSEC Not Provisioned in GoDaddy but Required By CloudFlare - Challenges Don't Pass

Help
1

Please fill out the fields below so we can help you better.

My domain is:ilesterg.net

I ran this command:/opt/letsencrypt/letsencrypt-auto certonly --standalone -d smtp.ilesterg.net

It produced this output:Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
tls-sni-01 challenge for smtp.ilesterg.net
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. smtp.ilesterg.net (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: SERVFAIL looking up A for smtp.ilesterg.net

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: smtp.ilesterg.net
    Type: connection
    Detail: DNS problem: SERVFAIL looking up A for smtp.ilesterg.net

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA 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.

My web server is (include version): N/A

The operating system my web server runs on is (include version):CentOS Linux release 7.3.1611 (Core), kernel 3.10.0-514.26.2.el7.x86_64

My hosting provider, if applicable, is:Amazon AWS

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

2

http://dnsviz.net/d/ilesterg.net/WWOGMQ/dnssec/
http://dnsviz.net/d/smtp.ilesterg.net/WWOHaA/dnssec/

The domain has a DS record indicating it uses DNSSEC, but it otherwise doesn’t use DNSSEC. Validating resolvers like those used by Let’s Encrypt will not be able to resolve it.

You need to remove the DS record at your registrar. Or enable DNSSEC on the DNS servers (and update the DS if necessary).

(The DS record looks like it’s from Cloudflare, but the domain is currently using GoDaddy nameservers.)

2 Likes
3

That did it! Thank you very much!

4

there is a step you have to take with GoDaddy if you enable DNSSEC on CloudFlare Servers

In case it crops up again the instructions can be found here: https://support.cloudflare.com/hc/en-us/articles/213586148-How-to-add-a-DS-record-to-GoDaddy

Andrei

5

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