0

This device is using NextDNS with no configuration

I have NextDNS enabled at the router level. I have a tp-link ac4000. I have IPv6 configured. I also have Linked IP setup as well.

I have 2 windows computers that both properly show that NextDNS is working via Chrome browser. These are connected with ethernet.

But, when I use my Google Pixel 2XL with Chrome it says that "This device is using NxtDNS with no configuration." I also have the same issue with the browser built into my Oculus Quest 2. These devices are connected via wireless.

My NextDNS account is setup with just a single configuration.

Any help would be appreciated.

6 replies

null
    • Roger_Wright
    • 3 yrs ago
    • Reported - view

    Have you configured  Private DNS on your Pixel?

      • Sterling_Heibeck
      • 3 yrs ago
      • Reported - view

      Roger Wright I can get it to work on my pixel if I install the app. But, I'm trying to figure out why it's not working at the router level. For my Quest 2, I can't install any app for it. I expected it to work at the router level. The really odd thing is, when I set it all up about 3 months ago, it looks like it was all working. So, I'm not exactly sure why it stopped. I'm wondering if it's the IPv6 stuff, which was an issue for OpenDNS as well.

      • Roger_Wright
      • 3 yrs ago
      • Reported - view

      Sterling Heibeck - Can you use the IPv4 settings rather than IPv6 and not worry about DNS encryption?

    • Ruby_Balloon
    • 3 yrs ago
    • Reported - view

    If you're able to use ipv6 endpoints at the router level, you don't need to link your ip as its for ipv4 only. Also did you modify chrome's secure dns settings on your pixel? If you selected "NextDNS" as your secure dns provider (via the dropdown) instead of entering your DoH endpoint, then you'll bypass your config when using that browser

    • Sterling_Heibeck
    • 3 yrs ago
    • Reported - view

    My Pixel was set to private dns (which I'm not sure how that happened, I didn't even know that was an option 😄). I turned that off and now it's picking up a profile for next dns. So, my last thing to figure out is why my Oculus Quest 2 browser is saying "using next dns with no configuration". I did turn off IPv6 just to see if it would help. It didn't. So, back to square one with that.

    know it was working at one point, because I tested it. Sure wish I knew how I got it to work the first time :shrug:

    Update: I just checked my wireless connection on my Quest 2 and I'm showing the addresses for next dns. So, it's using the proper DNS servers. 

    • Jay_Grider
    • 2 yrs ago
    • Reported - view

    I wanted to share the solution to this as I was having the same issues and just figured it out. 

    The problem comes from Chrome settings regarding private DNS. Specifically the issue occurs through this chain:

    1. User has both desktop and mobile (android confirmed, iOS unconfirmed) Chrome browser installed.

    2. User has enabled settings sync using Google account and Chrome for both mobile and desktop browsers.

    3. User enables private DNS on desktop chrome via DNS-over-HTTPS settings. 

    4. Chrome sync's the settings update to mobile browser, which for unknown reason changes the setting from custom provider to generic NextDNS provider on the mobile device.

    5. Even if user properly configured DNS-over-TLS in Android settings, those settings will be overwritten by Chrome's configuration on the device. (It appears in Android system DNS priority is Browser > VPN > System)

    6. To correct the issue simply clear the Chrome private DNS settings or change to match the correct settings. (unknown if clearing the mobile browser settings will clear the desktop browser settings since Chrome settings sync is apparently strange). 

Login to reply

Content aside

  • 2 yrs agoLast active
  • 6Replies
  • 1782Views
  • 3 Following