0

Block Page doesn't work in browser?

I've got the block pages turned on and the root CA installed on my device.

If I connect to nextdns from inside the browser's dns settings (using the instructions on the setup page) the blockpage won't appear, just the generic "this site can't be reached".

But if I connect to nextdns any other way (for example, setting it on Windows itself, or withh yogadns, or the CLI on the router) the block page works just fine. It's only setting it in the browser that doesn't work.

Is this expected behavior? Or am I doing something wrong?

4 replies

null
    • Martheen
    • 2 days ago
    • Reported - view

    Have you tried both Chromium-based and Firefox-based browsers?

      • Toad004
      • 2 days ago
      • Reported - view

        I didn't think that would make a difference, but I just tried it in Firefox and it actually works there. 

      It doesn't work in Chrome, Brave, or Edge (and I downloaded Chrome and made no other edits than the DNS setting itself just to see if it was something I did in brave or edge).

      • Toad004
      • yesterday
      • Reported - view

      Interestingly, going directly to blockpage.nextdns.io in Firefox results in "Great, blockpage.nextdns.io is not blocked anymore" (presumably because *.nextdns.io is in my allow list).

      blockpage.nextdns.io in any chromium browser returns "this site can't be reached".

    • Toad004
    • yesterday
    • Reported - view

    Disabling Ipv6 on the router appears to have resolved the problem. The Chromium browsers start showing the blockpage properly even with dns over https set in the browser.

    I have no idea why this made a difference.

Login to reply

Content aside

  • 8 hrs agoLast active
  • 4Replies
  • 46Views
  • 2 Following