As I use a VPN my “issue” may not be a real problem. I would like to use and I DO set the 188.8.131.52/184.108.40.206 in the Tap V9 VPN adapter and when checked CloudFlare does show as my DNS server. Later in the day, when I again check Who is my DNS server, GD google has “hijhacked” my settings and self assigns itself as my DNS server. wth over? Any help will be appreciated. (Using BitDefender Premium VPV - FYI)…
OR - Should my COMPLAINT be with BitDefender as I understand that a VPN will/Should set an appropriate DNS server to use??? Again, much thanks for any ideas…
If you are using some VPN client; then I would not recommend mixing things with their DNS servers and changing them to Cloudflare or someone else’s.
If so, I know Outline VPN which uses 220.127.116.11 and 18.104.22.168 in combination, but you do not change anything in the Tap Adapter of it.
Otherwise, I am afraid you could not get the connection to the Internet as right as it should be, neither protected, neither privacy would work.
And watch out for a kill switch option, after which actually you cannot connect to the Internet so easy at first.
Regarding 22.214.171.124/126.96.36.199 and a VPN client, I have in my main Ethernet Adapter where the custom DNS servers 188.8.131.52/184.108.40.206 are added. Therefore, while I used some VPN client (FastVPN, ProtonVPN), I did not have had to change anything else. Just connec to it (chosing some country) and it works like a charm. Same goes, when I am using Outline VPN (which indeed has got 220.127.116.11 and 18.104.22.168 for DNS servers).
Nevertheless, I am using Eset NOD32 Internet Security + Malwarebytes Premium. No issues at all at least for me (desktop PC - Windows 10 OS).
From your topic title, Google takes over the DNS servers - I assume that would have to be due to your VPN client and which DNS servers does it actually use (maybe you cannot affect them, as far as you do not have the access to the VPS server which is being configured and used that way - Google DNS, rather than some other like Cloudflare, etc., or actually is using secondary 22.214.171.124 instead of it’s primary 126.96.36.199 for some other reason as well).