0

openwrt https-dns-proxy on the router has stopped working - This device is using NextDNS with no profile.

At some point in the last few days, my whole-house router-based nextdns setup has stopped working.

For the past several years it has been operating perfectly via the openwrt https-dns-proxy configuration at router level, (meaning every device on my network benefits from the ad-blocking etc).

Without any changes at my end, I noticed that sites were suddenly riddled with ads. Upon checking the nextdns dashboard I see that my profile is now being ignored.

 

I'm a paid subscriber.

 

Here's the https-dns-proxy config - note profile ID suffix on the resolver URL.

Output from test.nextdns.io

 

The router dns has stopped working so TVs and Alexas and the like are no longer benefitting from the NextDNS service.

I see several recent reports of the same warning, but at device level.  This is at the router level.  It feels like something outside of my network has broken or changed. 

Please advise.  Thank you.

4 replies

null
    • Rob_Nightingale
    • 6 mths ago
    • Reported - view

    • Rob_Nightingale
    • 6 mths ago
    • Reported - view

    This post has some apparently relevant info

    zepto-sel-1 not working - Bug Reports - NextDNS Help Center

    • R_P_M
    • 6 mths ago
    • Reported - view

    The bootstrap DNS servers appear to be different from the profile Linked IP version, maybe that’s changed recently?

    Also try the **.28.0 & **.30.0 endings for bootstrap, see if that works or not. 

    • Rob_Nightingale
    • 6 mths ago
    • Reported - view

    Note for future searches - this was fixed by following this https://help.nextdns.io/t/60yhgjr/zepto-sel-1-not-working thread, and with the subsequent repair action to the zepto-lon-1 server.

Content aside

  • 6 mths agoLast active
  • 4Replies
  • 237Views
  • 2 Following