DNSSEC with own SOA and acme2


#1

I have 3 domains.
All three have their own zone for challenge.

zone _acme-challenge.example.net SOA IN SOA ns1.systron.de. info.systron.de. (
zone _acme-challenge.example.com SOA IN SOA ns1.systron.de. info.systron.de. (
zone _acme-challenge.systron.de SOA IN SOA ns1.systron.de. info.systron.de. (

systron.de has DNSSEC.

letsencrypt renewing works for example.net and example.com,
but not for systron.de.

letsdebug.net for systron.de shows me:

DNS response for _acme-challenge.systron.de had fatal DNSSEC issues: validation
failure <_acme-challenge.systron.de. TXT IN>: no signatures from 46.237.197.205

I like the way of seperating the zone in static and dynamic part.

Is there a solution for keeping my separation?


#2

Hi @rag

looks like the problem is solved. Letsdebug is green, same there:

https://dnssec-analyzer.verisignlabs.com/systron.de


#3

Letsdebug is red.

TXTRecordError
Fatal

An error occurred while attempting to lookup the TXT record on _acme-challenge.systron.de . Any resolver errors that the Let’s Encrypt CA encounters on this record will cause certificate issuance to fail.

DNS response for _acme-challenge.systron.de had fatal DNSSEC issues: validation failure <_acme-challenge.systron.de. TXT IN>: no signatures from 46.237.197.205


#4

Ok, I’ve used the wrong validation method. But if you use DNSSEC, then fix these errors:

https://dnssec-analyzer.verisignlabs.com/_acme-challenge.systron.de

_acme-challenge.systron.de
No DS records found for _acme-challenge.systron.de in the systron.de zone
No DNSKEY records found
No NSEC records in response
No RRSIGs found

#5

Why do Letsencrypt check domains on DNSSEC?


#6

Because the domain owner wants this.

Are you the domain owner of systron.de? Or why isn’t it possible to add the required records?


#7

Exactly. For certificate authorities, not issuing certificates that shouldn’t be issued is even more important than issuing certificates that should be issued. (That’s ultimately what makes the certificates useful to the end users who visit sites.) So Let’s Encrypt wants to use every source of information that can be checked automatically by machine that might help confirm whether the domain owner agrees with each certificate issuance request. DNSSEC is one source of information that can help confirm this, and in some cases help prevent the issuance of certificates that the domain owner didn’t want.


#8

I solved it. There are misconfigurations in my DNSSEC.
Thanks.


#9

Yep. Now your DNSSEC - configuration looks good.


closed #10

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