New Cloudflare 1.1.1.1 fastest, privacy-first consumer DNS service

Kari has also posted to the Win10.guru blog on the CloudFlare stuff. Please check it out at: 1.1.1.1 Win10.Guru.
Best wishes to one and all,
--Ed--

DooGie said:

Oh it is :)

Indeed. At first they claim - no logging, then, that they remove logs after 24 hours. So which is it? As for speed 9.9.9.9 and UltraDNS come close. As for privacy, I would go for something else, something less "corporate".

What I see:

Callender said:

What I see:

You should run a test with more queries. 2 is hardly enough, even you have 100ms difference.

Cliff S said:

Hey @Kari, I have everything,including my Fritz! Box set to Cloudflare now, except my vEthernet(virtual switch).
When I set my virtual switch, everything was ok, including internet access in my VMs.

But.... I

couldn't access my Fritz! Box then. I had to set the that one back to auto resolve

Ha, just figured out what the problem was for the vSwitch, thanks to Shawns tutorial using Get-DnsClientServerAddress.

The automatic resolve runs it through the Frit! Box, which I have set to Cloudflare anyhow.

When I copy and pasted 192.168.178.1 into the browser address bar, it takes me to my router/modems sign-in page.
So the unresolve was some kind of loop or something.

Another nice cmd to check your setting: nslookup
Nslookup

Using it since yesterday announcement by @Brink, amazing!

Cliff S said:

Another nice cmd to check your setting: nslookup
Nslookup

Ok, Cliff...what am I doing wrong. NSLOOKUP goes nuts, but the Powershell cmd works fine. Yes, it was an Admin Command prompt.

Code:

C:\Users\dhubb\Desktop>nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  2606:4700:4700::1111

>

--------------------------------------------------------------------------

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32>  Get-DnsClientServerAddress ethernet

InterfaceAlias               Interface Address ServerAddresses
                             Index     Family
--------------               --------- ------- ---------------
Ethernet                             9 IPv4    {1.1.1.1, 1.0.0.1}
Ethernet                             9 IPv6    {2606:4700:4700::1111, 2606:4700:4700::1001}


PS C:\WINDOWS\system32>

f14tomcat said:

Ok, Cliff...what am I doing wrong. NSLOOKUP goes nuts, but the Powershell cmd works fine. Yes, it was an Admin Command prompt.

Code:

C:\Users\dhubb\Desktop>nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  2606:4700:4700::1111

>

--------------------------------------------------------------------------

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32>  Get-DnsClientServerAddress ethernet

InterfaceAlias               Interface Address ServerAddresses
                             Index     Family
--------------               --------- ------- ---------------
Ethernet                             9 IPv4    {1.1.1.1, 1.0.0.1}
Ethernet                             9 IPv6    {2606:4700:4700::1111, 2606:4700:4700::1001}


PS C:\WINDOWS\system32>

I couldn't tell you. nslookup works fine for me in PS and CMD
nslookup gives you the server name along with the ip address is all


I have my modem and Ethernet adapter configured, but not my vSwitch(that connects straight through my Fritz! Box which has the new DNS settings).

I used this for a while then websites wouldnt load so had to switch back.