search

robin-thoni / certbot-pdns

Authenticator plugin for certbot
38 stars 10 forks source link

don't send request for wildcard #7

Closed 42phoenix42 closed 6 years ago

42phoenix42 commented 6 years ago

if use certbot like this, he send 2 separate TXT records to pdns and then he can't verify record certbot certonly --authenticator certbot-pdns:auth --noninteractive --agree-tos --email test@example.com -d "*.example.com" -d example.com

robin-thoni commented 6 years ago

I'm not really sure to understand the problem. From what I know, you're supposed to add one TXT record per requested domain. Moreover, @Zoddo, in #5, seems to be able to generate a wildcard certificates. Can you explain a little bit more what's the problem and how preventing the TXT record to be added fixes the problem?

lowEagle commented 6 years ago

I am successfully using this version of the plugin to generate wildcard certificates or similar to your case a wildcard certificate side by side with the base-domain.

Just like @robin-thoni I am not sure if I'm understanding your situation correctly.

However I'm running the certification process always twice (with just a few seconds in between) because the first attempt always fails due to a wrong dns verification. The second attempt always succeeds.

As this workaround works fine for me, I have not yet investigated the cause of this. Maybe you stumbled upon it? But I'm not sure if you can verify both, the wildcard and the root-domain, using only one TXT record.

42phoenix42 commented 6 years ago

I'm sorry maybe the problem was in missed A record at ns2. I tried to reproduce the error, but all is ok. If an error occurs again I will write in more detail.

42phoenix42 commented 6 years ago

With 1 TXT record, I successfully received the certificate in the example from 1 message

certbot certonly --authenticator certbot-pdns:auth --noninteractive --agree-tos --email test@example.com -d "*.example.com" -d example.com