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

Human Filterable Public Resolver List #15

Closed
ghost opened this issue Mar 13, 2018 · 4 comments
Closed

Human Filterable Public Resolver List #15

ghost opened this issue Mar 13, 2018 · 4 comments

Comments

@ghost
Copy link

ghost commented Mar 13, 2018

I have seen issue #4 and the stamp calculator, as well as the text based list of public resolvers. However I couldn't find an easy way to find suitable resolvers from the list. For example, if I wanted to find all servers in Canada that support DNSSEC, do not log, and do not censor, is there any easy way to generate such a list?

The list at dnscrypt.info does allow for sorting but not filtering, and does not include location as a sortable or filterable field.

@jedisct1
Copy link
Member

Having a map in addition to the list would be fantastic.

If we want to put that on dnscrypt.info, there are quite a few map components for Vue that all look great.

I can whip up an API that takes a set of IPs and returns their location using GeoIP.

Do you want to work on the map itself?

@ghost
Copy link
Author

ghost commented Mar 13, 2018

I wouldn't know where to begin with the mapping, but would be happy with just country info and simple filtering. Even an unstamped list would help with making an educated decision about server selection.

@jedisct1
Copy link
Member

jedisct1 commented Apr 4, 2018

@jedisct1 jedisct1 closed this as completed Apr 4, 2018
@ghost
Copy link
Author

ghost commented Apr 4, 2018

Would it be possible to have a non-stamped list? The stamp essentially hides important information that people could [or perhaps should] use to make educated decisions about which resolvers to use.

The map is pretty... but does not provide much information, hides multiple servers in a single location (I think), and in some cases appears to be just plain incorrect.

@DNSCrypt DNSCrypt locked and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant