Aminda Suomalainen
859cc89436
At the moment I am having problem with mikaela.info being in HSTS preload list and when I begun this list, I was hoping to use something conflict free and thought that mikaela.info would be the least bad choice while reading the reserver domains. Now I have searched on the issues more and encountered .internal TLD that seems to be what I am after and I hope it will become official. https://github.com/wkumari/draft-wkumari-dnsop-internal I think I can change these addresses safely as I am not using them anywhere as I worry about accidentally sending them to the internet and that opening new problems. This will mainly benefit me with web browsers, I hope. I will still have to link other people to direct IPv6 addresses that won't change with the platforms I use or mikaela.info will not be in the HSTS preload lists at time I need it. I wouldn't memorize IPv4 addresses though or start telling them someone in quick chat. |
||
|---|---|---|
| .. | ||
| README.md | ||
| dnscrypt-proxy.toml | ||
| hosts-mikaela.txt | ||
README.md
My configs for [dnscrypt-proxy]
At the time of writing, hosts-mikaela.txt is intended for hypothetical scenario where I have no access to DNS, but for some reason having access to [Yggdrasil] and/or [Hyperboria] or just to answer the question, why to rely on centralized technology on decentralized web.
The domains in hosts-mikaela.txt should also work without the file, relying on DNS (with the exception of nxdomain.mikaela.info which point is to not exist and confirm dnscrypt-proxy working properly), but that way you must trust DNSSEC, CloudFlare and wherever the CNAME points to who may not have DNSSEC.