Specify resolver source breaks CNAME adblocking

[darkdh]

Caused by brave/brave-core#7731 for fixing DoH leak
And the resolver only checks local cache for CNAME request and we will only get DNS_CACHE_MISS error for empty cache on Linux reported by @antonok-edm but it did resolved for me on macos after clearing dns cache

[darkdh]

after brave/brave-core#8262 is landed and uplifted to release.
We should test on different platforms to figure out what still doesn't work
and disable CNAME adblocking when DoH is enabled on those platforms

[LaurenWags]

labelling as QA/Blocked until this is uplifted

[kjozwiak]

Uplifted via brave/brave-core#8287 (review) & brave/brave-core#8288 (review).

[stephendonner]

Verification PASSED on macOS Big Sur using the following build:

Brave	1.22.65 Chromium: 89.0.4389.90 (Official Build) (x86_64)
Revision	62eb262cdaae9ef819aadd778193781455ec7a49-refs/branch-heads/4389@{#1534}
OS	macOS Version 11.2.3 (Build 20D91)

No DoH leak

Prerequisite: Followed https://wiki.wireshark.org/TLS and set up environment

Using the STR mentioned via brave/brave-core#8279 (comment), ensured that there weren't any DNS queries leaked when visiting https://tools.ietf.org:

CNAME adblock

DoH disabled

Disabled	Without filters	Filters applied

DoH automatic

Automatic	Without filters	Filters applied

Cloudflare

Cloudflare	Without filters	Filters applied

NextDNS

NextDNS	Without filters	Filters applied

---

Verification passed on

Brave | 1.23.68 Chromium: 90.0.4430.51 (Official Build) (64-bit)
-- | --
Revision | 32e5fa33a31641bded70a90e60121060691e7125-refs/branch-heads/4430@{#927}
OS | Windows 10 OS Version 2004 (Build 19041.867)

Verified the test plan from brave/brave-core#8279

No DoH leak

Ensured that there weren't any DNS queries leaked when visiting https://tools.ietf.org:

CNAME adblock

DoH disabled

Disabled	Without filters	Filters applied

DoH automatic

Automatic	Without filters	Filters applied

Cloudflare

Cloudflare	Without filters	Filters applied

NextDNS

NextDNS	Without filters	Filters applied

---

Verification passed on

Brave	1.23.69 Chromium: 90.0.4430.61 (Official Build) (64-bit)
Revision	dced74d4124b26b14126b611853d33512b60c7b6-refs/branch-heads/4430@{#1115}
OS	Ubuntu 18.04 LTS

Verified the test plan from brave/brave-core#8279

No DoH leak

Ensured that there weren't any DNS queries leaked when visiting https://tools.ietf.org:

CNAME adblock

DoH disabled

Disabled	Without filters	Filters applied

DoH automatic

Automatic	Without filters	Filters applied

Cloudflare

Cloudflare	Without filters	Filters applied

NextDNS

NextDNS	Without filters	Filters applied

[srirambv]

Verification passed on OnePlus 6T with Android 10 running 1.22.66 x64 build

• Verified test plan from Only specify net::HostResolverSource::DNS when DoH is enabled brave-core#8279

DoH Automatic

Android.ARM.DoH.Automatic.mp4

DoH OpenDNS

Android.ARM.DoH.Open.DNS.mp4

DoH CloudFlare

Android.ARM.DoH.Cloudflare.mp4

---

Verification passed on Samsung Tab A with Android 10 running 1.22.66 x64 build

• Verified test plan from Only specify net::HostResolverSource::DNS when DoH is enabled brave-core#8279

DoH Automatic

Android.Tab.DoH.Automatic.mp4

DoH OpenDNS

Android.Tab.DoH.OpenDNS.mp4

DoH CloudFlare

Android.Tab.DoH.CloudFlare.mp4

[bsclifton]

Moving to 1.23 after manually reverting from 1.22.x with brave/brave-core@f20e8ba

The fix for this appears to be causing #14721 on all channels