Daz put this in chat, at the top of the forum , but it looks so good that I thought it better go down here so we can discuss it more thoroughly. Things get buried up in chat very quickly https://anonymz.com/?https://blog.cloudflare.com/announcing-1111/ ...T
Moved from the google dns to this one some hours ago and so far so good. Pinging Google dns gives me a 39ms delay and cloudflare is 9ms here in portugal and I haven't seen any "resolving address..." on chrome's status bar. Let's see if it's keeps its stability when a lot of people start using this service
Performing really nice here on izzi (cable provider). I set 1.0.0.1 as preferred and 1.1.1.1 as alternative.
I have AT&T and the question: Changing DNS entries on Pace PLC 5268AC router Answer: You can't. Of course I can change it on my pc, but that would be useless if I can not change the DNS on my AT&T gateway. (if I do not want AT&T tracking where I go)
The answer is router cascading, a second router with a second subnet to which you point all your devices, and with the dns you want programmed into it. Only the devices you directly connect to the Pace will use it's dns. ...T
I won't be using this. I really don't like the idea of using Cloudflare any more than I have to (yes, I know this site uses it) I use my provider's upstream DNS which is untainted by ads etc., is really fast, and validates DNSSEC.
My internet and television service goes through the Pace router (AT&T U-Verse) , and it's DNS is required for the tv. I'll have to wait until I can get back onto Comcast with my own router
Right, connect the tv only to the pace router, and it will be happy connect everything else to the cascaded router which will bypass the pace to get it's own dns I came by this trick by accident cause my cable comes into the basement, where the tv is, and the router doesn't do wifi very well down there so I put a cat5 up to the office and made all my computer connections there necessity is the mother of invention. ...T
Here's some software to benchmark various DNS. You'll need to remove the dead ones and add 1.1.1.1 and 1.0.0.1 to the list. Firefox will soon support DNS-over-HTTPS and Cloudflare will probably be the default.
They're currently testing it in the nightly releases. If you had it installed and searched for "network.trr" in about:config you'd see some of the options. It'll also tell you if the TRR (Trusted Recursive Resolver) is being used in about:networking.
@Daz ok so I can remove FF beta and reinstall nightly release and after I show my results right thanks for the info
@Tiger-1 You'd only use a TRR if you wanted to increase your privacy. You probably don't want to do that at the moment. I've only mentioned it here because it's nice to have an alternative to Googles DNS-over-HTTPS. By the way, you did click on "Run Benchmark", right?
yep ok but I always trust in who really know what are doing also see my complete bench now using FF 61.0a1
DNS Resolvers Performance compared: CloudFlare x Google x Quad9 x OpenDNS https://medium.com/@nykolas.z/dns-r...flare-x-google-x-quad9-x-opendns-149e803734e5
Cloudfare and a local OpenDNS servers were the fastest ones for me (north europe), so I am using a such server mix at the moment.
I do not see how I can connect my router first and then to my Pace modem/router. That Pace modem uses AT&T's DNS to pick up the U-Verse tv channels..... or am I missing something here? If I attempt another DNS then I will lose service.
