Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Improve DNS settings #1134
Instead of just a low-level pref.vpn.dns, we could improve DNS settings and provide people with an option to choose from a pre-defined list of DNS servers.
Eventually, we could add DNSCrypt support.
Custom DNS Server
Please note how "Custom DNS settings" item is divided into two parts. The switch is tappable independently of the "Custom DNS" part.
IC: So, in general, the OS would show as the source. Anyway to track via different mechanism who's asking the OS? &, whenever it can be determined by whatever method, to note that in logs? Problem is, DNS requests "leak," even from apps that are ostensibly blocked from mobile/wifi data, & that can be used for tracking via, e.g., specially crafted host/DNS requests.
Shrewd trackers would simply block that by making that part of important domain — so, e.g., image.example.com, www.example.com, whatever.example.com, imageS.examples.com & myriad other useful subdomains, interspersed w/ fgkgsdhy.example.com, ahg.example.com jtdgjtgghftyy.example.com, random-letter-conglomerate.example.com, &c for nefarious purposes.
I've seen something quite like this for ad-serving/tracking.
What syntax is used for blocking subdomains, while whitelisting randomized useful 1s?
referenced this issue
May 9, 2017
This was referenced
Jun 29, 2017
@nkartyshov I forgot about two important things.
The last thing left to do -- change the matching algorithm. We don't need the full-scale matching for the DNS filtering, so we'd better replace it with something relatively simple.
Basically, we need to support the very basic syntax described in these two sections: