[GH-ISSUE #388] Suggest inclusion to public suffixes list #293

New issue

Closed

opened 2026-02-26 10:30:37 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 10:30:37 +03:00

Owner

Originally created by @Snawoot on GitHub (Oct 26, 2018).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/388

Originally assigned to: @ThomasWaldmann on GitHub.

Some major DNS providers ban public domains registered in nsupdate because of spammers.

There is a way to reduce impact: if parent domain will be added into public suffix list, all subdomains shall be considered as owned by distinct administrators and bans will be more granular. Also, inclusion into public suffix list is essential for cookie security: in this case browsers will isolate domains properly.

Other dynamic DNS services actually include their domains into this list:

user@pc:~$ curl -s https://publicsuffix.org/list/public_suffix_list.dat | fgrep dyndns
// DynDNS.com : http://www.dyndns.com/services/dns/dyndns/
dyndns-at-home.com
dyndns-at-work.com
dyndns-blog.com
dyndns-free.com
dyndns-home.com
dyndns-ip.com
dyndns-mail.com
dyndns-office.com
dyndns-pics.com
dyndns-remote.com
dyndns-server.com
dyndns-web.com
dyndns-wiki.com
dyndns-work.com
dyndns.biz
dyndns.info
dyndns.org
dyndns.tv
dyndns.ws
go.dyndns.org
home.dyndns.org
dyndns.ddnss.de
dyndns1.de

Since only owner of domain may include it into public suffixes list, your service can only suggest owners to do that. I think some hint to domain owners will be useful (or even may be enforced as requirement for new public domains).

Originally created by @Snawoot on GitHub (Oct 26, 2018). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/388 Originally assigned to: @ThomasWaldmann on GitHub. Some major DNS providers ban public domains registered in nsupdate because of spammers. There is a way to reduce impact: if parent domain will be added into [public suffix list](https://publicsuffix.org/), all subdomains shall be considered as owned by distinct administrators and bans will be more granular. Also, inclusion into public suffix list is essential for cookie security: in this case browsers will isolate domains properly. Other dynamic DNS services actually include their domains into this list: ``` user@pc:~$ curl -s https://publicsuffix.org/list/public_suffix_list.dat | fgrep dyndns // DynDNS.com : http://www.dyndns.com/services/dns/dyndns/ dyndns-at-home.com dyndns-at-work.com dyndns-blog.com dyndns-free.com dyndns-home.com dyndns-ip.com dyndns-mail.com dyndns-office.com dyndns-pics.com dyndns-remote.com dyndns-server.com dyndns-web.com dyndns-wiki.com dyndns-work.com dyndns.biz dyndns.info dyndns.org dyndns.tv dyndns.ws go.dyndns.org home.dyndns.org dyndns.ddnss.de dyndns1.de ``` Since only owner of domain may include it into public suffixes list, your service can only suggest owners to do that. I think some hint to domain owners will be useful (or even may be enforced as requirement for new public domains).

kerem closed this issue

2026-02-26 10:30:37 +03:00

kerem commented

2026-02-26 10:30:38 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 26, 2018):

our domains are on that list, since about a year or so.
we can't add 3rd party domains, you need to contact their owner.

@ThomasWaldmann commented on GitHub (Oct 26, 2018): our domains are on that list, since about a year or so. we can't add 3rd party domains, you need to contact their owner.

kerem commented

2026-02-26 10:30:38 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 26, 2018):

TODO: add a hint to "add domain" form.

@ThomasWaldmann commented on GitHub (Oct 26, 2018): TODO: add a hint to "add domain" form.

kerem referenced this issue

2026-02-26 10:31:34 +03:00

[PR #313] [MERGED] Update to Django 1.11 LTS #457