Public Suffix List amandm...
Public Suffix List amandment
- Home
- Control Panel
- Community Forum
- Services
- Dynamic DNS Service
- Public Suffix List amandment
- Community Forum
- Public Suffix List amandment
Topic: Public Suffix List amandment
Hello everybody,
your DDNS service is really great, but I have a suggestion to make it even better.
I think most of you have heard about Let's Encrypt?
I'm using that to get certificates for my DDNS domains, free and hassle-free. :)
However, this only works for my dynu.com DDNS. Every other domain fails, because too many people already requested certificates.
BUT there is a possibility to make it work:
Let's Encrypt evaluates requested domains against the "Public Suffix List", a list that contains both public (TLDs) and private (DDNS etc.) domains that are considered somewhat "top level".
If you would put your DDNS domains onto this list, all problems would be gone.
All that's necessary is a pull request to the GitHub repo and one TXT record for each domain for ownership verification. The precise process is described here:
https://github.com/publicsuffix/list/wiki/Guidelines
Unfortunately, 3rd parties are explicitly forbidden to do this for somebody else, so you (the devs) must do this, I can't help here.
Pretty sure this would be a great deal for some users.
Kind regards!
Michael
your DDNS service is really great, but I have a suggestion to make it even better.
I think most of you have heard about Let's Encrypt?
I'm using that to get certificates for my DDNS domains, free and hassle-free. :)
However, this only works for my dynu.com DDNS. Every other domain fails, because too many people already requested certificates.
BUT there is a possibility to make it work:
Let's Encrypt evaluates requested domains against the "Public Suffix List", a list that contains both public (TLDs) and private (DDNS etc.) domains that are considered somewhat "top level".
If you would put your DDNS domains onto this list, all problems would be gone.
All that's necessary is a pull request to the GitHub repo and one TXT record for each domain for ownership verification. The precise process is described here:
https://github.com/publicsuffix/list/wiki/Guidelines
Unfortunately, 3rd parties are explicitly forbidden to do this for somebody else, so you (the devs) must do this, I can't help here.
Pretty sure this would be a great deal for some users.
Kind regards!
Michael
Reply with quote | Report
Thank you for the feedback.
We have already sent a pull request to add our domain names to PSL at https://github.com/publicsuffix/list/pull/447 but the request is yet to be processed.
We have already sent a pull request to add our domain names to PSL at https://github.com/publicsuffix/list/pull/447 but the request is yet to be processed.
Reply with quote | Report
The pull request was not yet merged because the domain sorting is invalid. Guidelines specify sorting by TLD, currently the sorting is purely domain-alphabetical.
Reply with quote | Report
michaelmbezpn wrote:The pull request was not yet merged because the domain sorting is invalid. Guidelines specify sorting by TLD, currently the sorting is purely domain-alphabetical.
Reply with quote | Report
Author | Topic: Public Suffix List amandment |
---|---|
michaelmbezpn Joined: 4/5/2017 |
Public Suffix List amandment Friday, May 12, 2017 1:42 AM
Hello everybody,
your DDNS service is really great, but I have a suggestion to make it even better. I think most of you have heard about Let's Encrypt? I'm using that to get certificates for my DDNS domains, free and hassle-free. :) However, this only works for my dynu.com DDNS. Every other domain fails, because too many people already requested certificates. BUT there is a possibility to make it work: Let's Encrypt evaluates requested domains against the "Public Suffix List", a list that contains both public (TLDs) and private (DDNS etc.) domains that are considered somewhat "top level". If you would put your DDNS domains onto this list, all problems would be gone. All that's necessary is a pull request to the GitHub repo and one TXT record for each domain for ownership verification. The precise process is described here: https://github.com/publicsuffix/list/wiki/Guidelines Unfortunately, 3rd parties are explicitly forbidden to do this for somebody else, so you (the devs) must do this, I can't help here. Pretty sure this would be a great deal for some users. Kind regards! Michael |
xiaoye Joined: 3/27/2015 |
Public Suffix List amandment Sunday, May 14, 2017 4:09 PM
Thank you for the feedback.
We have already sent a pull request to add our domain names to PSL at https://github.com/publicsuffix/list/pull/447 but the request is yet to be processed. |
michaelmbezpn Joined: 4/5/2017 |
Public Suffix List amandment Monday, May 15, 2017 1:50 AM
Nice! :)
Keep up the good work guys! |
michaelmbezpn Joined: 4/5/2017 |
Public Suffix List amandment Tuesday, June 20, 2017 10:45 AM
The pull request was not yet merged because the domain sorting is invalid. Guidelines specify sorting by TLD, currently the sorting is purely domain-alphabetical.
|
timothytw Joined: 5/2/2002 |
Public Suffix List amandment Friday, June 23, 2017 10:02 AM
|
timothytw Joined: 5/2/2002 |
Public Suffix List amandment Tuesday, July 11, 2017 12:25 PM
The pull request has been merged.
|
It is currently Tuesday, December 24, 2024 7:56 PM US Mountain Standard Time
Tuesday, December 24, 2024 7:56 PM