0

I can't use Nextdns on both OS Wide and Browser at the same time. (nextdns issue)

Hi, i have set nextdns on my router, i also use it on my vpn tunnel (via DoH or DoT) and i also want to set it in my browser.

 

But when i have nextdns set in my vpn tunnel, if i set its DoH in either Firefox or Chromium, the browser can't open any websites.

 

This issue was from a long time ago but because of some private issues i never coud report it untill now.

 

This is really annoying.

 

In the past, when i had set nextdns in private dns of android (Android Pie that private dns didn't replaced other dns resolvers that set in the apps (in opposite to Android 10+), then i also set it in browser, it also didn't worked in browser and browser couldn't load any website (dns error)

 

Also you can test with intra app on Android and then set the DoH address of nextdns also on browser, then when you test it, it won't work at all.

 

The browser always show dns related issues unless i remove or change one of the DoH addresses to another resolver or remove one of them (and i don't want to do that as i use different configurations for browser and OS and i heavily spend time to create good configuration for each of them to better protect my workflow but it doesn't work.

 

Why you limited it like this? Or maybe a bug that haven't got your attention untill now?

 

Please fix this.

This is really annoying.

 

P.S: of course i have and use only one account (i wanted to mention this to avoid unnecessary questions)

 

P.S 2: i don't use private dns for a long time (Maybe two years?) (it set to OFF)

 

BTW, Thank you for very good service.

 

Please fix this very annoying issue.

Thanks.

Regards.

2 replies

null
    • redditisfun
    • 2 yrs ago
    • Reported - view

    There is also another issue like this, i have commented there that may explain this behavior better maybe?!

     

    https://help.nextdns.io/t/83hw7hn/chrome-dns

     

    This is my explanation:

     

    What in the replies are true"just when private dns is not off"

     

    But nextdns have this issue for a long time.

     

    You can test this using this method:

     

    1. Install "intra" app.

     

    2. Set your nextdns DoH address in it and turn it on.

     

    3. Then set another DoH (another profile that you have created for your browser or maybe same profile that you have set in the intra app)

     

    Then chrome/Firefox/etc can't browse any other websites.

     

    Seems like nextdns banned using its dns on multiple levels (router > OS > browser)

     

    These options won't get in conflict with each other.

     

    Just private dns on Android 10+ will get in conflict with other dns that you will set in android because it will replace those. (Google intentionally did this (to maybe avoid dns leaks or such))

     

    But using nextdns on vpn (or something like intra) and then using it in browser because you have set up different settings for each one and created different profiles with different settings in you account for each usage (OS, Browser, Router, etc)

     

    This behavior won't get into any conflict.

     

    You can test it by changing one of the dns resolvers to any other public resolver that exist.

     

    But we don't want to do that.

     

    We want to get layered protection for each level of our usage and unfortunately nextdns have bug or intentionally blocked this (i can't understand why if they did this intentionally though)

    • redditisfun
    • 2 yrs ago
    • Reported - view

    Edit: by using the word "profile", i was mean configuration.

Login to reply

Content aside

  • 2 yrs agoLast active
  • 2Replies
  • 309Views
  • 1 Following