acme when dns provider does not allow dns challenge

johnpoz

Ok - I just enabled dnssec on one of my domains I have pointed to cloudflare from namecheap... It took less than 2 minutes to setup.. And is working now and showing valid

tn1rpi3

@johnpoz I realize I've been trying this the hard way, relying on my current registrar. - I think I'll finally transfer the domain to Cloudflare. This limbo situation must end..

johnpoz

I know it sucks - but not all registrars are created equal that is for sure...

Have no issues with dnssec with namecheap or dynadot.. Namecheap was late to the table to even support it, but currently it seems to work real easy with simple to use gui..

I don't have anything with cloudflare as a registrar - but do have some domains pointing there.. And as you can see works real easy.. Now the domain I use for my plex is dnssec signed ;) hehehe

Gertjan

@tn1rpi3 :

Where did this one came from :

root@ns311465:~# whois 12bfree.com | grep 'DNSSEC'
   DNSSEC: signedDelegation
   DNSSEC DS Data: 60191 13 2 307DC191192735F5DF76FE364F6F6C1F18B108C43835315A74E450D64E4106A1

Never ever delete - on your local domain name server - references to this '60191' DS.
Rotating KSK keys is a real sport.

tn1rpi3

@Gertjan My best guess is that this is old data from before I transferred to Cloudflare. When I rechecked today (yes, the registrar was sluggish once again) the grep on whois finall returned the correct DS entry. -- On the other hand the certificate renewal still fails when the process arrives at the subdomain *.12bfree.com returning "invalid domain". Under SERVICES/ACME Certificates I entered *.12bfree.com for 'Domainname' - anything wrong with that, perhaps? BTW: a dig on e.g. lime.12bfree.com is successful and returns an IP from the Cloudflare realm.

tn1rpi3

@johnpoz I was one small step away from transferring to Cloudflare as a registrar when World4You finally came up with a working config today (as usual taking their time to do so). - I fully agree on your impressions on Cloudflare. They've got a clean interface, their online documentation is flawless and their basic subscription is free of charge.

tn1rpi3

@johnpoz DNS SEC is working alright now. Interestingly, ACME Certificate renewal is not. The job finishes with an error saying 'domain not found'.
On a closer look parent-DS with algorithm 13 produces a valid chain of trust, but for 'TXT-entries' the check-up says 'perhaps wrong' for '_acme-challenge.12bfree.com.12bfree.com' and '_acme-challenge.www.12bfree.com.12bfree.com' (see screenshot)

ACME Certificates with Cloudflare does not allow for TXT entries to be used for ownership validation. It uses account ID, key + token.
I'm out of ideas..
BTW: For check-up I used https://check-your-website.server-daten.de/?q=12bfree.com this time.

johnpoz

well that sure doesn't look correct... the _acme-challenge fqdn would be _acme-challenge.domain.tld.. you seem to have _acme-challenge.domain.tld.domain.tld and www.domain.tld.www.domain.tld not sure why you think those would work?

tn1rpi3

@johnpoz I fully agree; My API entries for domainname are 12bfree.com and *.12bfree.com
I don't see how the doubling could take place, unless I can't see the wood for all the trees..

johnpoz

Why not just manually create the TXT records in cloudflare?

I believe I am using acme for a cert via cloudflare - let me check, I know I played with it some time ago when I was doing reverse proxy through them... But might have killed it when I stop doing that..

edit: Yeah still using one, it renewed all not that long ago on its own, I didn't have to do anything..

This offloads the https for my ombi setup in haproxy.

edit2: here is what I have set in the acme client on pfsense

edit3: here it just renewed when I clicked the issue/renew button

tn1rpi3

@johnpoz Curious.
I left Token + Account ID empty, reran the script and wham-bam, success!
Thanks a lot for the screenshot!

Gertjan

You are using DNSSEC, so the resources needed to zone handling explode by a factor xx.
The entire zone has to be re signed.
The zone slave DNS server(s) are signalled that "something changed".
They - the slaves, when they see fit, come back to the master name server to "sync" the entire zone - the data needed to do so is also far - far more as a non-DNSSEC zone.

Keep in mind : those name servers that are "offered" to you when you rent a domain from a registrar are not blazingly fast. They are protected to deal with all the zone errors that are introduced these days ... they don't sync "as you want" - some take minutes or hours to do so.

The issue is : acme pfSense uses scripts - to update the remote dns server by whatever API the registrar made available. With this script - and settings to ID, the master DNS can be updated.
When done, the DNS-Sleep is needed, because, when Letenscrypt start to test, it could test the master DNS of your zone, or the slave (or one of the slaves). If they - the slaves - didn't sync (XFER'ed) yet, the cert request goes KO.

To make a long story short : set DNS-Sleep to 300 seconds, or more.

Of course, this story start to apply when all your settings are correct.

@tn1rpi3 said in acme when dns provider does not allow dns challenge:

I don't see how the doubling could take place, unless I can't see the wood for all the trees..

No trees, no wood.
It's "acme logs" ..... so : look at it - they are there to show the errors ^^
(one should only ignore logs when all is fine )

Proceed like this :
Locate acme the log file for the concerned domain.
Truncate it (make it zero byte size).
Do what needs to be done for renewing.cert.

Re open the log file, and admire the result.

Btw : be careful : 5 identical renewals for the same domain => your out for the week.

johnpoz

Great.. your all set then, cert and dnssec ;)

Been like a year or so sense set that up I think... I know I had done a wild card at one point, and was reversing plex through cloudflare at one point. But stopped doing that because some users were having issues.. And didn't have time to troubleshoot it, and I could not reproduce the problem on my end.. So I just turned it off and have not had time to go back to doing it that way.

But the ombi instance I have running for them to request stuff is still using acme cert. Which a few of them use and have not reported any issues... I get requests from it now and then for movies ;)

I was using the cloudflare as reverse proxy for some layer of protection for plex... But now I just changed the outside port and locked it to only NA IPs via pfblocker.. I am happy with the setup compared to just 32400 open to the planet ;)

edit: @Gertjan he moved his NS to cloudflare, so none of the slow registrars NS would be in play here.

tn1rpi3

@johnpoz Yeah, DNSSEC + certificate are in place now.
Big thanks to all who gave me their input; Special thanks again to you!

Next it's verifying my HAProxy settings on pfsense. -
The sites have been sitting on LXC instances for a while now.
Hope I can put them live in the near future.

I've played with plex in the past, but never used ombi. I went with Kodi for a couple of years until I mothballed it again. Sounds interesting, though.

I've hosted 12bfree.com before, but not in this constellation.
Previously, the cert renewal was a simple HTML 01 challenge with IP-Cop set to port-forwarding.
Additional sites were configured to show as subfolders.
That constellation was a lot quicker to set up..

tn1rpi3

@Gertjan said in acme when dns provider does not allow dns challenge:

I see how speed may become an issue here.

set DNS-Sleep to 300 seconds, or more.

I'll certainly remember that setting when needed.