2

Captive Portals

The NextDNS client is problematic when first connecting to networks such as captive portals.  In order to access networks such as Gogo inflight wifi, Starbucks WIFI, and many others, next dns has to be disabled first in order to allow the initial redirect to the captive portal page. After I accept the terms and gain internet access, I am able to reenable. 

Is there a method to allow these captive portal redirects without disabling Next DNS First?

3 replies

null
    • Jan.1
    • 3 yrs ago
    • Reported - view

    Instead of using the app you can type in your NextDns DNS over HTTPS URL  in Google Chrome, or other browsers like Edge, or Firefox. For example in Chrome click the three-dots settings icon.

    Choose Settings.

    Click Privacy and Security.

    Click and expand More.

    Click the toggle to enable Use Secure DNS and then select custom and type in your NextDns.

    • Jochen_H
    • 3 yrs ago
    • Reported - view

    I had the same problem and needed some time to identify NextDNS as root cause.

    At minimum please add some warning to the webpage, that NextDNS could interfere with captive portals!

    • Jack_M
    • 3 yrs ago
    • Reported - view

    I've had the issue.  Very frustrating.  I had to delete the NextDNS profile on my iPad in order to connect.

    I'm wondering if "DNS Rebinding Protection" being turned ON is causing this problem.  I'm tempted to turn it off and go to a local hotel here and see if it will start to work.

Login to reply

Content aside

  • 2 Likes
  • 3 yrs agoLast active
  • 3Replies
  • 658Views
  • 8 Following