# \[FYI\] Google / Chrome: "Experimenting with same-provider DNS-over-HTTPS upgrade"

**URL:** <https://discourse.pi-hole.net/t/fyi-google-chrome-experimenting-with-same-provider-dns-over-https-upgrade/23422>\
**Category:** Off topic\
**Created:** [September 11, 2019, 8:44am UTC](https://discourse.pi-hole.net/t/fyi-google-chrome-experimenting-with-same-provider-dns-over-https-upgrade/23422 "2019-09-11T08:44:08Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![craigphicks-public](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/craigphicks-public/32/42519_2.png) [@craigphicks-public](https://discourse.pi-hole.net/u/craigphicks-public)\
**Post date:** [July 21, 2024, 4:17pm UTC](https://discourse.pi-hole.net/t/fyi-google-chrome-experimenting-with-same-provider-dns-over-https-upgrade/23422/11 "2024-07-21T16:17:13Z")

</div>

I found that Chromium [Version 126.0.6478.182] is using DoH to tunnel ads DNS to get around PiHole, even if Chromium was set not to use DoH.

See details, and solution, in this post - [Chromium bypasses Pi-Hole by tunneling via DoH - solution is to block google.dns](https://discourse.pi-hole.net/t/chromium-bypasses-pi-hole-by-tunneling-via-doh-solution-is-to-block-google-dns/71330)

---

_[View the full topic](https://discourse.pi-hole.net/t/fyi-google-chrome-experimenting-with-same-provider-dns-over-https-upgrade/23422)._