RS500 Firmware Version 1.2.7.2 released

Your testing on a Orbi system? RBR50 series or your RBR750 series? 

This is observed with my RS500 router immediately after the latest firmware update.

And was happening on prior version as well?

coolwifi wrote:

This is observed with my RS500 router immediately after the latest firmware update.

My post was asking on what CrimpOn is currently using. I believe he's on Orbi system and also doesn't exhibit the 3rd DNS issue on Orbi as you first posted about with not seeing the 3rd DNS entry on the WEB UI however behind the scenes in FW is still running. 

Yes, I am using an original RBR50 Orbi router, which does not exhibit that bizarre addition of a CloudFlare DNS serve. (Nor does the RBR750.)  It appears (to me) that the latest RS500 firmware is flawed and there is no obvious workaround.  The discussion wandered off topic with the introduction of https://browserleaks.com/dns

Those 100 ipv4 DNS server addresses are the ip's of the actual physical DNS servers used by cloudflare and Google based on your location. Cloudflare and Google do have a cluster of DNS nodes distributed throughout the world.

Okay, the previous firmware version for the RS500 router didn't exhibit this issue.

CrimpOn wrote:

What I cannot seem to grasp is the mechanics behind gathering this information.

Here's the trick:

Browserleaks has its own authoritative DNS nameserver set up for some of its subdomains (something like xxxx.dns4.browserleaks.com).  Its web page tells your browser to make background requests to  a bunch of randomly generated hosts using those subdomains.  This results in a flood of DNS requests, so multiple resolvers in the clusters end up servicing them.

Because the hostnames are randomly generated (on the fly), they won't be in resolver cache - so each request ends up going to the BrowserLeaks nameserver. That tells BrowserLeaks the IP addresses of the specfic resolvers in the cluster that were used. 

CrimpOn wrote:

It appears (to me) that the latest RS500 firmware is flawed and there is obvious workaround.

I don't see any replies from coolwifi​ on what happened when he added a third DNS resolver to his config.  So it is premature to say there is a workaround.

I had replied earlier mentioning that whatever DNS I set as the third DNS server, cloudflare DNS gets automatically added as one of the additional DNS servers by the router.

Ok thank you for this latest information. 
Something I have noticed on Orbi BE systems and I think AX systems as well about a year ago, noticed that when first setting up a system, DNS seemed to be Google DNS being set on the RBR web UI. I hadn't really been concerned about it as I mostly use ISP DNS or custom Quad 9. Usually DNS is set to my ISP DNS which is Sparklight. They use a 24.xx address for there DNS. Now wondering if this is something being seen across both NH and Orbi systems when setting up from factory defaults. I'll check into this with my RS and Orbi systems and see what I find. 

As we know there maybe a bug with your initial post about the 3rd DNS entry that is not visible from the UI. We've make NG aware of this and is under review and aware of it.

StephenB wrote:

So it is premature to say there is a workaround

Crap.  Sorry about the typo.  Should read, "

CrimpOn wrote:

there is NO obvious workaround.

Had hoped that filling in all three DNS server choices would "push the 1.1.1.1 out".

So looking at my RS600 today, seeing this as default as I guess I had updated FW and had not changed it since last factory reset and setup from scratch:

I'm seeing 3 user changeable DNS sections here:

After setting to Quad9 and SparkLight, it's showing here as being set:

Testing MS EDGE with browserleaks site finds the following: 

Test Results Found 39 Servers, 3 ISP, 1 Location

1 from Cableone.Net which is Sparklight now.

6 from WoodyNet.Inc

Rest all from Cloudfare 

All locations from Seattle. 

Thanks for testing. Can you change the DNS setting to  get automatically from ISP and share the DNS settings page? Looks like you have already configured cloudflare as the third DNS before updating the FW?

Just as I thought, it's picking the CF and Google DNS and not the ISP DNS when set to automatic:

Was the cloudflare DNS added by the router? How about the automatic DNS setting?

Was set by the router when I select Automatic for DNS. 

Same thing is happening on my RS700 as well: