[GH-ISSUE #224] put nsupdate.info onto public suffix list #199

Closed
opened 2026-02-26 09:36:29 +03:00 by kerem · 6 comments
Owner

Originally created by @ThomasWaldmann on GitHub (Dec 5, 2015).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/224

Originally assigned to: @ThomasWaldmann on GitHub.

https://publicsuffix.org/
https://community.letsencrypt.org/t/dyndns-no-ip-managed-dns-support/883/11

check what cookies we use ourselves.

check whether this influences letsencrypt certificate issuance.

Originally created by @ThomasWaldmann on GitHub (Dec 5, 2015). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/224 Originally assigned to: @ThomasWaldmann on GitHub. https://publicsuffix.org/ https://community.letsencrypt.org/t/dyndns-no-ip-managed-dns-support/883/11 check what cookies we use ourselves. check whether this influences letsencrypt certificate issuance.
kerem 2026-02-26 09:36:29 +03:00
  • closed this issue
  • added the
    task
    label
Author
Owner

@ThomasWaldmann commented on GitHub (Dec 26, 2015):

current state: we set 2 cookies for nsupdate.info: sessionid and csrftoken.

so we first need to migrate the main site to www.nsupdate.info, set the cookies there and then get onto that list.

<!-- gh-comment-id:167356039 --> @ThomasWaldmann commented on GitHub (Dec 26, 2015): current state: we set 2 cookies for nsupdate.info: sessionid and csrftoken. so we **first** need to migrate the main site to www.nsupdate.info, set the cookies there and **then** get onto that list.
Author
Owner

@ThomasWaldmann commented on GitHub (Dec 28, 2015):

https://github.com/publicsuffix/list/pull/93

looking at the list of all pull requests there, it seems this could take longer. please add any requests about when it will be added there to the pull requests linked above.

<!-- gh-comment-id:167581293 --> @ThomasWaldmann commented on GitHub (Dec 28, 2015): https://github.com/publicsuffix/list/pull/93 looking at the list of all pull requests there, it seems this could take longer. please add any requests about when it will be added there to the pull requests linked above.
Author
Owner

@elnappo commented on GitHub (Jan 5, 2016):

https://github.com/publicsuffix/list/pull/100

<!-- gh-comment-id:169019172 --> @elnappo commented on GitHub (Jan 5, 2016): https://github.com/publicsuffix/list/pull/100
Author
Owner

@elnappo commented on GitHub (Apr 19, 2016):

nsupdate.info and nerdpol.ovh is now on the list.

<!-- gh-comment-id:211931229 --> @elnappo commented on GitHub (Apr 19, 2016): nsupdate.info and nerdpol.ovh is now on the list.
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 19, 2016):

\o/

Now let's see how long it takes letsencrypt to use the latest list...

<!-- gh-comment-id:211934133 --> @ThomasWaldmann commented on GitHub (Apr 19, 2016): \o/ Now let's see how long it takes letsencrypt to use the latest list...
Author
Owner

@ThomasWaldmann commented on GitHub (Sep 6, 2023):

This is how the _psl txt records should look like:

_psl.nsupdate.info.	3600	IN	TXT	"https://github.com/publicsuffix/list/pull/93"
_psl.nerdpol.ovh.	3600	IN	TXT	"https://github.com/publicsuffix/list/pull/100"
<!-- gh-comment-id:1708335902 --> @ThomasWaldmann commented on GitHub (Sep 6, 2023): This is how the `_psl` txt records should look like: ``` _psl.nsupdate.info. 3600 IN TXT "https://github.com/publicsuffix/list/pull/93" _psl.nerdpol.ovh. 3600 IN TXT "https://github.com/publicsuffix/list/pull/100" ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsupdate.info-nsupdate-info#199
No description provided.