-
Notifications
You must be signed in to change notification settings - Fork 103
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
Change default solver method for wildcard domains #110
Comments
Thanks for the feedback! If you are interested by doing a PR on this, don't hesitate to ping me here or on the Symfony Slack: I'd be glad to help :) . |
How do you validate wildcard domains using In my case all the sub-domains lead to same document root so |
You have to use a DNS solver. |
Theoretically Will it? |
I'm using Gandi.Net. It has API (see http://doc.livedns.gandi.net/) were you can:
|
Sounds 5. Could you please submit a Pull Request? |
I probably could, but I wonder how do I test that. In the test suite I haven't found examples of DNS solver test classes. Also maybe you can point me to the correct test case where I can see how challenge fixtures are used. Generating certificates right on Let's Encrypt just to test how it works sounds like a terrible idea. |
I don't think resolver should be DNS by default when wildcard identifier occur. |
Running
bin/acme authorize '*.domain.ext'
gives following error -In such case, acmephp should set
dns
as default resolver(If the domain starts with *)if user specifies any non-dns solver, then error should be thrown that non-dns solvers are not allowed by acme in wildcard domains.
The text was updated successfully, but these errors were encountered: