search

v2ray / Planning

Deprecated. Please use v2ray-core for feature requests
60 stars 13 forks source link

[DELETED] #24

Closed amtlib-dot-dll closed 6 years ago

amtlib-dot-dll commented 7 years ago

[DELETED]

S-Tsunemori commented 7 years ago

I think this feature is more useful than this docker-related use-case. Being able to use DNS-over-HTTPS api of Google Public DNS maybe is maybe the only way to get correct result in areas can't access 8.8.8.8 directly.

The current suggested way of using Google Public DNS is redirect 8.8.8.8:53 to local using Dokodemo-door. It works but has a big flaw: some domains (mostly cdn services) would be resolved to an IP-address that is good for (v2ray)server but slow or even inaccessible for clients, due to the fact that server and client locate in a different geographical positions.

Surely you can access those sites through the proxy, then it will result in many unnecessary proxy accesses. On the other hand, using DNS-over-HTTPS API this problem can be solved by including edns_client_subnet parameter that points to the same subnet of client, so this cdn problem won't exist.

DarienRaymond commented 6 years ago

The edns_client_subnet feature is also available on UDP-based DNS query, right?

DarienRaymond commented 6 years ago

This issue will be fixed after https://github.com/v2ray/Planning/issues/27 gets fixed.