Archived
🌐 Website Issue | Add more encrypted DNS servers #1077
Closed
opened 2019-08-01 09:40:02 +00:00 by Mikaela
·
11 comments
No Branch/Tag Specified
master
dependabot/bundler/nokogiri-1.13.6
dependabot/bundler/addressable-2.8.0
freddy-m-patch-3
pr-add_RemoveMyPhone_sponsor
pr-browser_cleanup_1257_1328_1430
freddy-m-patch-2
freddy-m-patch-1
pr-vpn_hated_one_video
cdn
update-nitrohorse-image
promote-metager-to-card
hardware
pr-add_azirevpn
pr-add_mailfence
shop
1673
pr/1658
i18n-simple
sponsorship-edits-nov2019
i18n
ipfs
blacklight447-ptio-patch-3
blog
remove-windows-icons
pr/1147
i18n-testing
add-beautify
No results found.
Labels
Clear labels
:mag:🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
approved, waiting for a PR
Pull requests that update a dependency file
The Invisible Internet Project (I2P)
Operating Systems
A label for stalebot if it gets added
Anything related to media streaming.
Anything covering the Tor network
active work in progress, do not merge or PR (yet)!
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
Extensible Messaging and Presence Protocol
Matrix protocol
Browser Extension related issues
Correction of content on the website
Firefox & forks, about:config etc.
Anything primarily related to site cleanup.
Virtual Private Network
*Technical* issues with the website.
Domain Name System
Anything covering a translated version of the site
Milestone
No items
No Milestone
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1077
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
Currently all DNS servers have warnings and we only list 4. I had been wondering if there really are no others than what we list, Google and Cloudflare, but there is a long list. I have no idea where I picked my previous list and I apologize.
Short list of what may be worth looking at:
http://neutopia.org/- missing privacy policyhttps://tenta.com/dns-setup-guides- I am not sure on their policy of counting counters and their privacy policy has the "information we don't collect" section and they talk about supporting law enforcement whentalking about VPN, so I am not sure if the DNS should be listed either.This is based on the dnsprivacy.org list, from which homepages or additional information I found very easily by just checking the main domain.
As there are starting to be options, maybe regional ones can join the list too
The larger the list grows, I’m wondering if it makes sense to create a new table like the Email and VPN providers have?
Assigning to Nitrohorse who agreed to take this/tablesizing on Wire
Me at Reddit, maybe this should also be said on the site?
^^ hmm, yeah, I think that's a good callout.
How's this for the columns / DNS resolver criteria for a new table?
Found this helpful reference from DNSPrivacy also: https://dnsprivacy.org/jenkins/job/dnsprivacy-monitoring/
We could add an alert like how the VPN table has:
Slightly off-topic, but what are the requirements to be considered for the list?
I am working on an open-source DNS resolver which can be seen over here, but would love to know if I need to add support for DoH and/or DoT, for example.
The closest we have to rules is https://github.com/privacytoolsIO/privacytools.io/pull/1097#issuecomment-518189915 , but we are yet to actually commit/document them anymore.
I think supporting DoH/DoT would be preferable as there are already public lists of DNSCrypt providers (so I see it as a nice bonus) as it's not a standard and requires a specialized software like dnscrypt-proxy while DoH (the original motivation for the issue) is supported natively by Firefox (and hopefully soon Chromium) while DoT is supported natively by Android 9 and systemd-resolved (and I know Windows 10 feedback hub has multiple requests for it).
Hm, going to look into adding DoH and DoT, then. I was mostly trying not to if I am honest, but with Firefox and Android 9 Pie going that route, it seems impossible to keep ignoring it.
We already have multiple DNSCrypt servers, and our central DNS server connects to them and use them as resolvers, but I will see about adding DoH and DoT support as well.
Thanks, @Mikaela! :)
Source on Chromium going to support DoH in the future: https://bugs.chromium.org/p/chromium/issues/detail?id=908132#c5