4 ms·
If appropriate for your use case, you can get your domain added to the public suffix list [1]. Then the restrictions no longer apply. This has side-effects wi
by jewel 11y ago
If appropriate for your use case, you can get your domain added to the public suffix list [1]. Then the restrictions no longer apply.
This has side-effects with browsers and cookies so you wouldn't want to do it on a domain without understanding the impact.
[1]: https://github.com/publicsuffix/list/blob/master/public_suffix_list.dat https://github.com/publicsuffix/list/blob/master/public_suff...
P.S. In the unlikely event that someone involved is reading this, PLEASE make this a DNS attribute that is set on the top-level domain instead, in a TXT record perhaps. It's silly that we have to have a globally coordinated and distributed list for this data.
- pfg 11y ago> P.S. In the unlikely event that someone involved is reading this, PLEASE make this a DNS attribute that is set on the top-level domain instead, in a TXT record perhaps. It's silly that we have to have a globally coordinated and distributed list for this data. The Dbound WG[1] was working on this, but sadly didn't seem to get anywhere. [1]: https://tools.ietf.org/wg/dbound/ https://tools.ietf.org/wg/dbound/