add nsupdate.info dyndns service

[ThomasWaldmann]

we (and users of our nsupdate.info service) ran into issues with letsencrypt.org's rate limiting for tls certificate requests.

it might also help for other purposes, so people can know these hosts do not all belong to me / to the nsupdate.info domain, but shall be considered independent.

[ThomasWaldmann]

We would appreciate if this entry could be added quickly, as this is blocking TLS adoption by all our subdomains. Also, we would like to request letsencrypt certificates for our service also and we are locked out from that / we ran into the rate limit currently, because that entry is not on the list yet. Thanks!

[ghost]

Any news on this?

[zackp30]

I would also like this.

[shaula]

+1
Can we somehow speed up the process? Is anything missing?

[sleevi]

Sorry for the delays @ThomasWaldmann

Can you please update this patch according to https://github.com/publicsuffix/list/wiki/Guidelines

Specifically

• Rebase to master
• Remove the date
• Indicate how you would prefer to authenticate this request (preferably, via DNS TXT record)

[ThomasWaldmann]

rebased, removed date and i am working on setting up the txt record for auth.

TODO: set this up:

$ dig TXT _psl.nsupdate.info
https://github.com/publicsuffix/list/pull/93

[ThomasWaldmann]

OK, txt record is set up. Please validate. :)

[sleevi]

Validated via TXT

[ThomasWaldmann]

Thanks! BTW, do you know how often the letsencrypt guys update the list from your repo?

[sleevi]

No.