The servers that are showing in the test results you have provided are utilizing VyprDNS. The majority of our servers will not be named specifically ‘VyprDNS’ so that they cannot be identified as a VPN DNS server by services or sites within the country of the VPN endpoint you are using. To elaborate a little bit on how VyprDNS works and other reasons why you may be seeing the hosts you are seeing on dnsleaktest.com.
We setup VyprDNS in such a way that prevents our customer’s DNS queries from being associated with their activity on VyprVPN. Doing this prevents organizations that restrict DNS from putting blocks in place for our users. This is done using a DNS relay system. Sites like dnsleaktest.com will see the last server in the DNS relay chain, which typically does not identify itself with Golden Frog services. This is good because customer DNS is not identified as coming from VyprVPN, which is the intended goal.
The hostnames associated with those last server DNS IPs are not typically within our control, so we normally cannot change them. That’s why you are seeing IPs associated with Query Foundry (dns-cac-lb-02.rr.com) and etc… However, if you ping dns-cac-lb-02.rr.com you will notice a completely different IP resolve. That’s the actual server IP, not the one on dnsleaktest.com. This discrepancy is the unfortunate result of improper reverse DNS information outside of our control.
DNS leak test sites make the faulty assumption that the DNS server to which the end-user makes the request is the actual DNS server from which the leak test will see the request, which is not how it works with VyprDNS, specifically because we don’t want leak test servers seeing the request come from VyprVPN.
We go to great lengths to ensure all data sent over our network stays between Golden Frog and the customer. Our specific configuration of VyprDNS is just one of the ways we protect your data.
With regards to your concern about improper geolocation as shown on that DNS test site.
Please note that we host DNS in the country our VPN servers are located in. I explained why users might see odd or concerning information on that site above.
We have found no issues at this time on our end regarding the geolocation of our DNS. If DNS test sites are showing information different from what is expected, it could be due to a number of factors on the site’s end, including use of outdated geo-ip databases.
I hope I was able to shed some light on your concerns. I definitely understand where you’re coming from in wanting to know more about the results you are seeing. If you are still encountering DNS-related issues you suspect might be further related to geolocation, please contact our support team or see our geo-blocked site troubleshooting article.