Compatibility with let's ...
Compatibility with let's encrypt
- Casa
- Pannello di controllo
- Forum della Comunità
- Services
- Dynamic DNS Service
- Compatibility with let's encrypt
- Forum della Comunità
- Compatibility with let's encrypt
Argomento: Compatibility with let's encrypt
Hi there,I am using your ddns service to get some hostnames like something.dynu.net.I am also using Let's encrypt https://letsencrypt.org/ which provides free verified certificates using some semi-automatic verification of domain control, which relies on interactions with let's encrypt serverLet's encrypt has set a rate limit of 20 requests per week on a given domain, for fair usage enforcement. This means that all the users that use dynu.net are sharing a global limit of 20 requests, which is very limitative. Essentially, if you request and get your public suffix (such as dynu.net, and the tens of others you provide as option) into the "public suffix list" that is used by let's encrypt, then this global limit of 20 requests per week will be applied at the subdomain level (so something.dynu.net would have a 20 rate limit, as well as any other *.dynu.net).For more details, you can look at those tickets:https://github.com/publicsuffix/list/issues/98https://github.com/publicsuffix/list/issues/88Please, make sure this email is read by some engineers that will understand the issue, and escalate that above for decisions.I am happy to assist you guys in this process.Cheers
Rispondi con citazione | Segnalare
Thank you for your feedback. We will look into having this implemented.
Rispondi con citazione | Segnalare
We have created a pull request to have our domain names added to the PSL. You may view the PR at https://github.com/publicsuffix/list/pull/447.
Rispondi con citazione | Segnalare
Hi, PSL replied 3 days ago for dynu.com to comply with their Guidelines. Pls do so as i would also like to generate a SSL CERT for dynu.net ddns! :DQUOTEPlease ensure this PR complies with the Guidelines (https://github.com/publicsuffix/list/wiki/Guidelines)END QUOTE
timothytw wrote:We have created a pull request to have our domain names added to the PSL. You may view the PR at https://github.com/publicsuffix/list/pull/447.
Rispondi con citazione | Segnalare
itadminwmck wrote:Hi, PSL replied 3 days ago for dynu.com to comply with their Guidelines. Pls do so as i would also like to generate a SSL CERT for dynu.net ddns! :DQUOTEPlease ensure this PR complies with the Guidelines (https://github.com/publicsuffix/list/wiki/Guidelines)END QUOTEtimothytw wrote:We have created a pull request to have our domain names added to the PSL. You may view the PR at https://github.com/publicsuffix/list/pull/447.
Rispondi con citazione | Segnalare
timothytw wrote:We have created a pull request to have our domain names added to the PSL. You may view the PR at https://github.com/publicsuffix/list/pull/447.
Rispondi con citazione | Segnalare
Thanks for getting this merge request through. Reading through its history, things sure were harder than they should have been.Thanks again.
Rispondi con citazione | Segnalare
Autore | Argomento: Compatibility with let's encrypt |
---|---|
Chris zeva Iscritto: 21/04/2017 |
Compatibility with let's encrypt martedì 25 aprile 2017 15:47
Hi there,I am using your ddns service to get some hostnames like something.dynu.net.I am also using Let's encrypt https://letsencrypt.org/ which provides free verified certificates using some semi-automatic verification of domain control, which relies on interactions with let's encrypt serverLet's encrypt has set a rate limit of 20 requests per week on a given domain, for fair usage enforcement. This means that all the users that use dynu.net are sharing a global limit of 20 requests, which is very limitative. Essentially, if you request and get your public suffix (such as dynu.net, and the tens of others you provide as option) into the "public suffix list" that is used by let's encrypt, then this global limit of 20 requests per week will be applied at the subdomain level (so something.dynu.net would have a 20 rate limit, as well as any other *.dynu.net).For more details, you can look at those tickets:https://github.com/publicsuffix/list/issues/98https://github.com/publicsuffix/list/issues/88Please, make sure this email is read by some engineers that will understand the issue, and escalate that above for decisions.I am happy to assist you guys in this process.Cheers
|
timothytw Iscritto: 02/05/2002 |
Compatibility with let's encrypt mercoledì 26 aprile 2017 10:14
Thank you for your feedback. We will look into having this implemented.
|
timothytw Iscritto: 02/05/2002 |
Compatibility with let's encrypt mercoledì 3 maggio 2017 13:21
We have created a pull request to have our domain names added to the PSL. You may view the PR at https://github.com/publicsuffix/list/pull/447.
|
itadminwmck Iscritto: 11/05/2017 |
Compatibility with let's encrypt domenica 18 giugno 2017 06:24
Hi, PSL replied 3 days ago for dynu.com to comply with their Guidelines. Pls do so as i would also like to generate a SSL CERT for dynu.net ddns! :DQUOTEPlease ensure this PR complies with the Guidelines (https://github.com/publicsuffix/list/wiki/Guidelines)END QUOTE
|
timothytw Iscritto: 02/05/2002 |
Compatibility with let's encrypt domenica 18 giugno 2017 19:34
|
blackbarret Iscritto: 26/04/2017 |
Compatibility with let's encrypt lunedì 19 giugno 2017 05:55
|
timothytw Iscritto: 02/05/2002 |
Compatibility with let's encrypt martedì 11 luglio 2017 12:26
The pull request has been merged.
|
CornHulio Iscritto: 19/11/2017 |
Compatibility with let's encrypt domenica 19 novembre 2017 06:39
Thanks for getting this merge request through. Reading through its history, things sure were harder than they should have been.Thanks again.
|
Al momento è venerdì 13 dicembre 2024 06:17 US Mountain Standard Time
venerdì 13 dicembre 2024 06:17