-
-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Chrome exempting itself form macOS settings #19
Comments
@chew-z First more complicated, is to use the config file or command (read doc of your browser) to tell the browser he must disable this feature. Second is to use as a source (For the profile) A server who block all url of DNS server. And third is to go the NEXDNS repository, search their list of all known secure server and copy past it in the hosts of Mac. |
@paulmillr Since it's not a bug in .mobileconfig file I ask this issue be closed. |
@BirdInFire
Can you explain the third option you mentioned? Are you saying that NextDNS maintains a public list of DNS entries for all known secure DNS providers? |
Gift : https://github.com/nextdns/metadata/blob/master/parentalcontrol/bypass-methods |
@Jikodis note : if you plan tu use Apple relay (for safari + DNS resolution) when Mac OS 12 will be there you must remove the two first domain from it mask.icloud.com |
Apple relay will bypass nextdns so if you use it mobileconfig will not be used you can try it with dns leak |
I know i tell him about relay to not see an issue later because of the host tweak |
The following instructions are given by Mullvad.net for Chrome-based browsers. https://mullvad.net/en/help/dns-over-https-and-dns-over-tls#macos
|
In blog post Firefox is mentioned but not Chrome.
It might then come as a surprise to some users that Chrome will exempt itself from global settings on macOS (of course) and will use its own DNS-over-https. If someone would like to setup DoH on Chrome this is how to do it:
Go to Settings-> Privacy and Security --> Security and scroll down to Use Secure DNS. Check this option and select predefined server (Google, Cloudflare) or use your own.
Chrome 87 on Big Sur 11.0.1
The text was updated successfully, but these errors were encountered: