# \[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:** 8

<div class="post-metadata">

**Author:** ![pidohole](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/958977/32.png) [@pidohole](https://discourse.pi-hole.net/u/pidohole)\
**Post date:** [September 11, 2019, 5:27pm UTC](https://discourse.pi-hole.net/t/fyi-google-chrome-experimenting-with-same-provider-dns-over-https-upgrade/23422/8 "2019-09-11T17:27:05Z")

</div>

It's not speculative. If the current dns has a corresponding DoH server then Chrome will automatically switch to DoH. How does Chrome determine if there's DoH server available? It's has a list of supported DoH servers:

- Cleanbrowsing
- Cloudflare
- DNS.SB
- Google
- OpenDNS
- Quad9

This is straight from the horse mouth. [https://www.chromium.org/developers/dns-over-https](https://www.chromium.org/developers/dns-over-https)

---

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