As long as I read the document of letsencrypt, it seems that the maximum number of certificates per domain depends are related on the suffix list. It should be related for the domains. But “.jp” TLD seems to be restricted as being bundled one domain. For example, all of DDNS service in japan which have .jp suffiex got already limitation. I’m not administrators of the DDNS service but I hope to use them. Should I ask the administrators for this issue? Or can I request to somewhere to fix the strange restrict?
Definitely not the case.
You should ask the owners of the DDNS .jp domains to apply to the PSL, this is how they can avoid the rate limitations.
For example, if you want to issue
test.ddns.jp with separate rate limits, then
ddns.jp needs to be on the PSL. Hope that makes sense.
Thanks your quick reply. I’ll ask owner of DDNS service to add the domain to PSL.
The owner send PR to PSL. Thanks. BTW, how long does it take that new rate limit will be enabled?
The big question is how much time will pass before the pull request is merged into the Public Suffix List. I’m not able to speculate about that, but you can look at other recently merged pull requests as examples.
After that, the publicsuffix-go library will be updated, Let’s Encrypt’s Boulder software will be updated, and then Let’s Encrypt will have to deploy it. You may need to ask the Let’s Encrypt developers to perform the update, but that part of the process usually takes about 1-2 weeks.
good to hear that. thanks for your kindness.
I am not sure the PR is in the right format:
:on the first line has no spaces around it.
- The email is not in the proper format (
- The email line does not start with
I would guess that it will definitely be rejected in its current state. To save time you might consider fixing these issues before it goes for review.
Publicsuffix pull request help
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.