3 ms·
It already does. This is the purpose of putting a DNS-over-HTTPS resolver into the browser, so you can't bypass it with local resolvers.
by dogecoinbase 7y ago
It already does. This is the purpose of putting a DNS-over-HTTPS resolver into the browser, so you can't bypass it with local resolvers.
- spaceribs 7y agoCouldn't I sign my own pi-hole and add the certificate to my phone/computer?
- mkl 7y agoNo use if e.g. Chrome hardcodes Google's servers and ignores the system ones.
- TrinaryWorksToo 7y agoCould you hardcode the ip addresses in your own NAT?
- yjftsjthsd-h 7y agoThis is, in fact, already sometimes necessary since there are things that will hard code 8.8.8.8.
- handzbagz1 7y agoSo you block access to Google's DNS (except for your local DNS server) on your router. And so the arms race continues.