RS500 Firmware Version 1.2.7.2 released

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.