acme when dns provider does not allow dns challenge

tn1rpi3

@johnpoz I just got a basic Cloudflare account. DNS settings at my provider now point to cloudflare servers, update is pending. - Acme settings for DNS-Cloudflare require 1. Cloudflare API Key, 2. API Email Address, 3. API Token and 4. API Account ID. --> I don't see any of these in my Cloudflare account though. Could you provide some Cloudflare wisdom, plz?

tn1rpi3

@johnpoz Transfer to Cloudflare nameservers is now completed. It took some five days (‘status pending)’, then I was able to retrieve the necessary API keys for DNS challenge. (btw: It would appear logical that you can't get them right away, my bad..) - I’ll be creating the certificate this weekend and report back if all went well.

tn1rpi3

@johnpoz Meanwhile my registrar has trouble getting the settings for DNSSEC right. I don't know why but I've been waiting for a working config since Nov. 18th. - Needless to say that I can neither update the certificate right now, nor is the site accessible at all.

johnpoz

Yeah its sad state affairs to be honest, since to be accredited its a requirement to support dnssec..

This was made a requirement back in 2013
https://www.icann.org/en/system/files/files/approved-with-specs-27jun13-en.pdf

Page 67

Registrar must allow its customers to use DNSSEC upon request by relaying orders to add, remove or change public key material (e.g., DNSKEY or DS resource records) on behalf of customers to the Registries that support DNSSEC. Such requests shall be accepted and processedin a secure manner and according to industry best practices. Registrars shall accept any public key algorithm and digest type that is supported by the TLD of interest and appears in the registries posted at: http://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xml and http://www.iana.org/assignments/ds-rr-types/ds-rr-types.xml. All such requests shall be transmitted to registries using the EPP extensions specified in RFC 5910 or its successors.

When I first fired up a dnssec back a few years with dyndot since they listed they supported it on xyz tld... It took a few emails to get them to correct their problems and get it working..

tn1rpi3

@johnpoz I'm glad it's become a matter of compliance by now. - I understand that unspoofable caller IDs add a great deal to the security on the net. According to this source one could even file a complaint with ICANN if a provider is unwilling/unable to provide DNSSEC. - Anyway, still waiting for something to happen..

johnpoz

Yeah the only thing is your tld has to support it.. Not the registrar's problem if the tld does not have it - and there are many out there that do not still.

It has gotten way better
http://stats.research.icann.org/dns/tld_report/
1517 TLDs in the root zone in total
1388 TLDs are signed;
1378 TLDs have trust anchors published as DS records in the root zone;

JeGr

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

I don't see any of these in my Cloudflare account though. Could you provide some Cloudflare wisdom, plz?

Cloudflare doesn't create an API key with your account, you have to do that for yourself. Click on your profile symbol/pic in the upper right corner of your CF Dashboard. Got to "my profile". Then access the API Tokens Tab. There check for or create the Global API Key. That's the one you need for the acme package with dns_cf mode. Works like a charme.

tn1rpi3

@johnpoz valid point. We're talking about a .com address here.

tn1rpi3

@JeGr thanks for the pointer!

johnpoz

Well .com has been dnssec for a long time ;) And every accredited registrar is required to provide the support to do dnssec.. So yeah you should be able to use any registrar - yet that is not the case for sure.. And while some say they support it - you can not get it to work ;)

You shouldn't have any issues with cloudflare..

tn1rpi3

@johnpoz I've requested a DS record at my current registrar and sent them the data Cloudflare has provided me with: It goes like
"example.com. IN DS 62910 7 1 1D6AC75083F3CEC31861993E325E0EEC7E97D1DD"
While my provider says they've done what's necessary, a website check produces the following error: Fatal error: DNSKEY 2371 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.
Did I overlook something here or is the ball back in the registar's court?

If the latter is the case, I'll initiate a domain transfer and do everything within Cloudflare. - The whole affair is taking way too long..

Gertjan

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

Did I overlook something here or is the ball back in the registar's court?

Looks like that's the case.
Use https://dnsviz.net/d/12bfree.com/dnssec/ - it's far more 'visual'..

Most registrars these days use GUI's so "you can help yourself" - or better : APIed everything.

The registrar will then your domain settings - most often fully automated.

While your at it, check you IPV6 glue.

tn1rpi3

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

Looks like that's the case.

I'm sorry, I don't understand.
There's no GUI at my registar's page. All I can do is send them the DS record data, which I did.

I'm trying to figure out if the registar made a mistake impementing the DS record, or if somethings missing on my side.

tn1rpi3

@tn1rpi3 To me it looks like the registar made a mistake implementing the DS record:
https://dnssec-analyzer.verisignlabs.com/12bfree.com
says something similar: "None of the 2 DNSKEY records could be validated by any of the 1 DS records"

Gertjan

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

Did I overlook something here or is the ball back in the registar's court?

My answer :

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

Looks like that's the case.

Valid for both answers, because I don't know what you overlooked (to hand over to the registrar) - it it most probably boils down to : it's up to the registrar to put your DS in place ....

Btw : how you hand this over ? By mail ? Seems rather dangerous to me.
If some one impersonates you nu y mail, your domain will disappear from the net.

Btw : DS operation do take time.

tn1rpi3

@Gertjan Thanks. I got it. -
I handed it over while logged in to their website (created a ticket) two days ago.

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.