3

Using NordVPN and NextDNS but DNS leak allowing VPN detection

I'm trying to watch Amazon Prime videos, but my combination of using NordVPN and NextDNS seems to have a leak that allows Amazon to detect my use of a VPN.  I've contacted NordVPN and their only suggestion is to use their DNS servers, which of course I do not want.

Does anybody have an idea on how to fix this?

15replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • This is certainly something many of us will run into in the future.  I will like and follow this to see if someone has an afternoon or full day off to play with it and discover it and share the solution.  Thanks fo r sharing Anson Li

    Like 1
  • I have the same problem with Express VPN. I also contacted them and told me I have to deactivate NextDNS if I want to use a VPN

    Like
  • Are you running an adblocker like uBlock Origin. If so try disabling it and see if the DNS leak stops.

     

    UBlock Origin version 1.34 added a Privacy setting "Uncloak Canonical Names" and turned it on by default. This causes uBlock origin to do resolve DNS queries itself and hence the leakage.

    This setting was previouly under "I am an advanced user" and was off by default.

    Like 2
  • I should also say I am running NordVPN and NextDNS and it works fine with no leakage, as I am sure will expressVPN

    Like
      • Anson Li
      • Anson_Li
      • 13 days ago
      • Reported - view

      Ian Morris What's your setup? I tried turning the setting and uBlock itself off and it doesn't work.

      Like
      • Ian Morris
      • Ian_Morris
      • 13 days ago
      • Reported - view

      Anson Li I am running uBlock in firefox; if you are using a Chrome browser uBlock works differently since Chrome doesnt have its own DNS API that Firefox has.  Have you tried disabling the uBlock extension just to test it (or temporarily uninstall it) - it worked for me. I would recommend you try firefox which works for me.

      Like
      • Anson Li
      • Anson_Li
      • 13 days ago
      • Reported - view

      Ian Morris Yeah i'm using Firefox. Disabling worked, like you said. Is there no way to get the same effect with changing some settings?

      Like
      • Ian Morris
      • Ian_Morris
      • 13 days ago
      • Reported - view

      Anson Li Like I said, I went into uBlock's Settings and unticked Uncloak Canonical Names (if you are using version 1.34 or later) - that should do the trick.

      Since I now run nextDNS on my router and redirect all DNS queries to it (using NAT rules) it is no longer an issue for me anyway.

      Like
      • Anson Li
      • Anson_Li
      • 13 days ago
      • Reported - view

      Ian Morris Actually, it seems even with it unchecked and disabled, Amazon still knows I'm on a VPN. I think when I tried it last my VPN was off.

      Like
      • Ian Morris
      • Ian_Morris
      • 13 days ago
      • Reported - view

      Anson Li It is easy to tell, certainly my router load "Known VPN Network IPs" on a hourly basis. So it would be able to tell from your source IP address. However, that is different from DNS leakage which is what I thought you were talking about earlier?

      Like
      • Anson Li
      • Anson_Li
      • 13 days ago
      • Reported - view

      Ian Morris I thought that DNS leak was the reason why Amazon can see if you're on a VPN or not.

      Like
      • Ian Morris
      • Ian_Morris
      • 12 days ago
      • Reported - view

      Anson Li I don't know how Amazon detect it but most organisations use the IP Ranges associated with the Autonomous Systems number of VPN providers.

      Like
  • don't use nordshitvpn please

    Like
  • Ian Morris  I tried to disable Ublock and I am using Firefox, but I still got a DNS leak with Express VPN. But more importantly, like Anson Li, streaming services detect the VPN. And I works perfectly if I disable Next DNS

    Like
      • Ian Morris
      • Ian_Morris
      • 11 days ago
      • Reported - view

      Maxime Menard It depends on how you are disabling Ublock, have a look at my earlier post about unticking "Uncloak canonical name" under uBlock's settings and retest. The DNS leakage is specific to uBlock on Firefox, since unlike Chrome it has a DNS API that uBlock can use.

      I would be very surprised if ExpressVPN is not compatible with nextDNS - when using a VPN service normally you would use the DNS Servers associated with the VPN and not nextDNS, when there is no VPN you would normally use nextDNS - if configured properly this switch is automatic. Also if you have configured the VPN to continue using nextDNS, then yes that show as a DNS Leakage (because it is going to a third party and not the VPN provider) but as long as your DNS traffic is encrypted, it shouldn't be an issue if you trust nextDNS, since no-one else can read your queries or replies. 

      Also detecting that you are using a VPN does not have anything to do with DNS leakage, since there are managed tables specifying the ip address ranges of VPN providers (again see my earlier post above). I use these table to prevent VPN connections being established on my secure network.

      Like
Like3 Follow
  • 3 Likes
  • 11 days agoLast active
  • 15Replies
  • 232Views
  • 5 Following