mirror of
https://github.com/paulmillr/encrypted-dns.git
synced 2026-08-12 22:20:24 +02:00
Update readme
This commit is contained in:
@@ -6,26 +6,23 @@ Configuration profiles for [DNS over HTTPS](https://en.wikipedia.org/wiki/DNS_ov
|
||||
|
||||
To add a new provider, or edit an existing one, edit json files in `src` directory.
|
||||
|
||||
### Caveats
|
||||
### Known issues
|
||||
|
||||
Known issues (we can't fix them, maybe Apple can):
|
||||
|
||||
1. Applications (e.g. Firefox in specific regions; App Store in all regions) can choose to ignore the system-level resolver and use their own.
|
||||
[Check out the discussion](https://github.com/paulmillr/encrypted-dns/issues/22).
|
||||
2. iCloud Private Relay, VPN clients & Little Snitch / LuLu will ignore the DNS profile.
|
||||
3. Command line tools that interact with DNS (e.g. `host`, `dig`, `nslookup`) won't use DoH -
|
||||
will use the DNS severs set in Network, or picked up from DHCP.
|
||||
4. [Wi-Fi captive portals](https://en.wikipedia.org/wiki/Captive_portal) in cafes, hotels, airports are exempted by Apple from eDNS rules; to simplify authentication - this is good
|
||||
5. TLS DNS is blocked more often by ISPs than HTTPS, because TLS uses non-standard port 853, which is easy to block.
|
||||
See [Google's article](https://security.googleblog.com/2022/07/dns-over-http3-in-android.html)
|
||||
|
||||
Check out [encrypted-dns over TOR](https://github.com/alecmuffett/dohot) if you need more privacy.
|
||||
1. Some apps and protocols will ignore encrypted-dns:
|
||||
- Firefox in specific regions, App Store in all regions. [More info](https://github.com/paulmillr/encrypted-dns/issues/22)
|
||||
- iCloud Private Relay, VPN clients
|
||||
- Little Snitch, LuLu
|
||||
- DNS-related CLI tools: `host`, `dig`, `nslookup` etc.
|
||||
2. [Wi-Fi captive portals](https://en.wikipedia.org/wiki/Captive_portal) in cafes, hotels, airports are exempted by Apple from eDNS rules; to simplify authentication - this is ok
|
||||
3. TLS DNS is easier for providers to block, because it uses non-standard port 853.
|
||||
[More info](https://security.googleblog.com/2022/07/dns-over-http3-in-android.html)
|
||||
4. e-dns over TOR could be better privacy-wise, but we don't have this for now.
|
||||
|
||||
## Providers
|
||||
|
||||
`Censorship=yes` (also known as "filtering") means the profile will not send true information about `hostname=IP` relation for some hosts.
|
||||
|
||||
| Name | Region | Censorship | Notes | Install (Signed - Recommended) | Install (unsigned) |
|
||||
| Name | Region | Censorship | Notes | Install | Install (unsigned) |
|
||||
| ------------------------------------------------------------------------------------ | ------ | ---------- | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
|
||||
| [360 Security DNS][360-dns] | 🇨🇳 | Yes | Operated by 360 Digital Security Group | [HTTPS][360-dns-profile-https-signed] | [HTTPS][360-dns-profile-https] |
|
||||
| [AdGuard DNS Default][adguard-dns-default] | 🇷🇺 | Yes | Operated by AdGuard Software Ltd. Blocks ads, tracking & phishing | [HTTPS][adguard-dns-default-profile-https-signed], [TLS][adguard-dns-default-profile-tls-signed] | [HTTPS][adguard-dns-default-profile-https], [TLS][adguard-dns-default-profile-tls] |
|
||||
@@ -81,28 +78,8 @@ macOS [(official docs)](https://support.apple.com/guide/mac-help/mh35561/):
|
||||
|
||||
If an earlier version of a profile is already installed on your Mac, the settings in the updated version replace the previous ones.
|
||||
|
||||
## Scope
|
||||
|
||||
There seems to be an [additional option](https://github.com/paulmillr/encrypted-dns/issues/22) that allows to use system-wide profiles. To try it, add this to mobileconfig file:
|
||||
|
||||
```xml
|
||||
<key>PayloadScope</key>
|
||||
<string>System</string>
|
||||
```
|
||||
|
||||
## Signed Profiles
|
||||
|
||||
In the `signed` folder we have signed versions of the profiles in this repository. These profiles have been signed by [@Xernium](https://github.com/Xernium) so that when you install the profiles,
|
||||
they will have a verified check box on the installation screen. It also ensures that these profiles have not been tampered with. However, since they were signed by a third party, they may lag behind their unsigned counterparts a little.
|
||||
The signature is valid until `2025-11-02`
|
||||
|
||||
Previous signatures by:
|
||||
[@Xernium](https://github.com/Xernium), replaced at `2024-11-01`
|
||||
|
||||
[@Candygoblen123](https://github.com/Candygoblen123), replaced at `2023-11-29`
|
||||
|
||||
[comment]: <> (We recommend that you install a signed profile instead of an unsigned profile because it ensures that it was not modified while it was downloading.)
|
||||
|
||||
To verify resolver IPs and hostnames, compare mobileconfig files to their documentation URLs. Internal workings of the profiles are described on [developer.apple.com](https://developer.apple.com/documentation/devicemanagement/dnssettings). In order to verify signed mobileconfigs, you will need to download them to your computer and open them in a text editor, because signing profiles makes GitHub think that they are binary files.
|
||||
|
||||
## On demand activation
|
||||
|
||||
Reference in New Issue
Block a user