Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace Open DNS with Quad9 #58

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Replace Open DNS with Quad9 #58

wants to merge 1 commit into from

Conversation

hellais
Copy link
Contributor

@hellais hellais commented Dec 6, 2017

No description provided.

@willscott
Copy link
Contributor

I'm not convinced this is any better. The large entities with motivation to run large/stable/open DNS infrastructure all have ulterior motives.

While Open DNS is cisco, which also sells DPI equipment,
Quad 9 is IBM and packet clearing house which are monetizing their feed by re-selling it, and using it for threat intelligence. Neither seem great for the end user.

i honestly think that probably the best public one to point to is probably 4.2.2.1, which is run by level3 as a quirk - it was originally just an easy-to-remember IP that ran an open DNS, and they saw how many people were using it and retrofitted it to be high reliability. They run it pretty quietly, and don't seem to make money off of it or sell the data as far as a cursory search shows.

https://www.tummy.com/articles/famous-dns-server/

@darkk
Copy link

darkk commented Dec 6, 2017

I'm opposed to changing one service provider to another service provider without clear reason (unless the provider sponsors OONI for promotion somehow 🤣).
I don't see anything supporting statement that Quad9 is a bit more privacy oriented than most.

Unless we have a procedure to express our preference in a verifiable way my suggestion is to take ALL services from wikipedia list and show all of them in shuffled order (or random two of them). Another option I like is to pick random two of them for every OONI Probe release to move the shuffling from OONI Probe runtime to build stage.

OONI should be neutral, huh?

The least thing I want is to advocate for one Open Resolver provider and against another one using something as vague as "Terms of Service" :-) Maybe we should test "censored" domain using all of the resolvers and suggest those one that are not affected. Or just compare the latency and suggest the nearest (probably, 8.8.8.8 will win in this case...).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants