Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wildcard certificate DNS #84

Closed
HampusNL opened this issue Sep 24, 2018 · 3 comments
Closed

Wildcard certificate DNS #84

HampusNL opened this issue Sep 24, 2018 · 3 comments
Assignees

Comments

@HampusNL
Copy link

When creating a certificate with wildcard in the DNS name it pushes that wildcard star in the name to the DNS provider. It doesn't seem to matter for us (Cloudflare), it works, but is that really how it should be doing? Cloudflare seems a bit angry with the format and say it's wrong.

bild

@rmbolger
Copy link
Owner

rmbolger commented Sep 24, 2018

What command did you use to generate that record? Normal wildcard records like *.example.com should be having the *. stripped and replaced by the _acme-challenge. portion.

@rmbolger rmbolger self-assigned this Sep 24, 2018
@HampusNL
Copy link
Author

Ahh sorry, you are completely right. Checked the timestamp now and that was an old record, probably a colleague have tested it before me on another platform. It creates the record _acme-challenge.domain.com as it should so everything good.

And thnx alot for this awesome module! Soon finished with the setup to replace most of our internal services with LE thanx to your module!

@rmbolger
Copy link
Owner

Not a problem. Glad to hear everything's working!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants