{"action":"created","issue":{"url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/115","repository_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy","labels_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/115/labels{/name}","comments_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/115/comments","events_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/115/events","html_url":"https://github.com/jedisct1/dnscrypt-proxy/issues/115","id":296129911,"number":115,"title":"Fallback resolver & Latency ","user":{"login":"CHEF-KOCH","id":727123,"avatar_url":"https://avatars2.githubusercontent.com/u/727123?v=4","gravatar_id":"","url":"https://api.github.com/users/CHEF-KOCH","html_url":"https://github.com/CHEF-KOCH","followers_url":"https://api.github.com/users/CHEF-KOCH/followers","following_url":"https://api.github.com/users/CHEF-KOCH/following{/other_user}","gists_url":"https://api.github.com/users/CHEF-KOCH/gists{/gist_id}","starred_url":"https://api.github.com/users/CHEF-KOCH/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CHEF-KOCH/subscriptions","organizations_url":"https://api.github.com/users/CHEF-KOCH/orgs","repos_url":"https://api.github.com/users/CHEF-KOCH/repos","events_url":"https://api.github.com/users/CHEF-KOCH/events{/privacy}","received_events_url":"https://api.github.com/users/CHEF-KOCH/received_events","type":"User","site_admin":false},"labels":[{"id":798777627,"url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":15,"created_at":"2018-02-10T20:12:02Z","updated_at":"2018-02-16T23:10:14Z","closed_at":null,"author_association":"NONE","body":"The greatest weakness of DNCrypt is for most people the latency, now we have a fallback resolver mechanism but the main issue isn't fixed. Whenever a resolver/server is slow it tries now to switch to another server, however, this is theoretically a good idea but in fact, it ends up with lots of roundtrips and you might see already in your Browser a DNS error until another resolver was found.\r\n\r\nI gave DNSCrypt-Proxy (as a test for an article) 5 different people with different skills and 4 made a complaint about the same thing, the latency. So how we are going to resolve this issue? My idea would be that there could be a check/configuration option to ensure the resolver is not slower than let's say 60 ms which would also already sort out lots of servers on the list.\r\n\r\nThe problem is that latency is really an important thing because most people which simply want to browse or play online games they care more about this part than the 'security' aspect, in most cases from what I know it ends up that people going to disable it for this time but a workaround to solve this would be a better solution.\r\n\r\nI would be thankful for ideas and a discussion ground because 'then disable it' is not really what I like to hear because that's still in my eyes a no-go. I do not really expect low-latency but at least no errors and or disconnects would be fine and I think lots of people could life with that."},"comment":{"url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/comments/366385004","html_url":"https://github.com/jedisct1/dnscrypt-proxy/issues/115#issuecomment-366385004","issue_url":"https://api.github.com/repos/jedisct1/dnscrypt-proxy/issues/115","id":366385004,"user":{"login":"jedisct1","id":124872,"avatar_url":"https://avatars2.githubusercontent.com/u/124872?v=4","gravatar_id":"","url":"https://api.github.com/users/jedisct1","html_url":"https://github.com/jedisct1","followers_url":"https://api.github.com/users/jedisct1/followers","following_url":"https://api.github.com/users/jedisct1/following{/other_user}","gists_url":"https://api.github.com/users/jedisct1/gists{/gist_id}","starred_url":"https://api.github.com/users/jedisct1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jedisct1/subscriptions","organizations_url":"https://api.github.com/users/jedisct1/orgs","repos_url":"https://api.github.com/users/jedisct1/repos","events_url":"https://api.github.com/users/jedisct1/events{/privacy}","received_events_url":"https://api.github.com/users/jedisct1/received_events","type":"User","site_admin":false},"created_at":"2018-02-16T23:10:14Z","updated_at":"2018-02-16T23:10:14Z","author_association":"OWNER","body":"```sh\r\n$ drill linuxjournal.cmail19.com @185.140.114.51\r\n\r\n;; ->>HEADER<<- opcode: QUERY, rcode: NXDOMAIN, id: 47678\r\n```\r\n\r\nNot even using DNSCrypt at all here. Looks like this resolver (CS Spain) is buggy or has been blacklisted by linuxjournal servers.\r\n\r\nNot sure why. I heard a while back that Cryptostorm was filtering some domain names. This might actually be the case, and the exact criteria are unclear.\r\n\r\nCan you try to confirm that with them? If they are filtering things, the `filtering` flag must be added to their properties."}}
{"actor":{"display_login":"jedisct1"}}