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 server

Let'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/98
https://github.com/publicsuffix/list/issues/88

Please, 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

Thank you for your feedback. We will look into having this implemented.

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.

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! :D

QUOTE

Please ensure this PR complies with the Guidelines (https://github.com/publicsuffix/list/wiki/Guidelines)

END QUOTE

Thank you for the information. We will work on this.

Awesome, very grateful for this decision !!!

The pull request has been merged.

Thanks for getting this merge request through. Reading through its history, things sure were harder than they should have been.

Thanks again.