2

Most common problem with NextDNS

The problem is with block page

Because of that page most banking apps don't work

Even some of old devices crush

Well

If you have discovered any main failure you don't see on NextDNS logs

Disable blockpage

I am suggesting you the best

15 replies

null
    • bithip
    • 2 wk ago
    • Reported - view

    Find this Block Page settings under:

    NextDNS Dashboard/Settings/Block Page.

      • TheAliDev
      • 2 wk ago
      • Reported - view

      i know bro

      • bithip
      • 2 wk ago
      • Reported - view

       

      That information is for someone who might land on this thread in the future and not be able to figure out where the NextDNS Block Page Settings configuration is. 

      I am familiar with NextDNS, but it took me a few minutes to locate the Block Page settings. 

      With the config location above, NextDNS users could save a lot of time.

      • TheAliDev
      • 2 wk ago
      • Reported - view

      ok

      No problem 

    • NextDNs
    • 12 days ago
    • Reported - view

    The block page is only served on blocked domains. If you have blocked domain in your logs, disabling the block page will be no-op, so it is hard to see how disabling would fix anything.

      • bithip
      • 12 days ago
      • Reported - view

       My best guess is that because enabling the "Block Page" feature prompts for NextDNS CA certificate installation for blocked dns query links inside the app, some apps might find it confusing to continue with normal operation.

      • TheAliDev
      • 3 days ago
      • Reported - view

       i know blockpage is great

      But it confuses many apps even devices of some vendors like Infinix by redirecting blocked queries to blockpage

      It even give self sign ssl that apps won't understand

    • mmir
    • 3 days ago
    • Reported - view

    Stumbled across this post. My iOS and iPad app store randomly won’t load and there is nothing on the logs that suggest anything blocking it. Switched off the block page and instantly the app store loaded, every time, on both iPad and iPhone.

    • hagezi
    • 3 days ago
    • Reported - view

    I've had so many issues that weren't issues, but were due to the activated block page. This "feature" should be banned.

    I point this out to users when they open an issue, but it is sometimes ignored anyway:

    Gerd - https://github.com/hagezi/dns-blocklists

      • NextDNs
      • 3 days ago
      • Reported - view

       would you have a technical explanation that could elucidate how the block page feature might be responsible for these issues?

      • hagezi
      • 3 days ago
      • Reported - view

       

      My reference was to the enabled block page for blocked domains. Some blocked trackers behave differently if a "valid" IP is returned instead of 0.0.0.0 or NXDOMAIN. This means that some trackers have to be unblocked when the block page is enabled, which is not necessary when the block page is disabled.

      There are probably also problems if the certificate is not installed, see also: https://github.com/yokoffing/NextDNS-Config?tab=readme-ov-file#block-page

      • NextDNs
      • 3 days ago
      • Reported - view

       it would be intriguing to debug cases where issues arise. This feature is quite popular, and we're only receiving a relatively small number of complaints about broken websites or apps. We've never encountered one such case ourselves. Perhaps some apps react poorly to invalid certificates in the case the user did not trust the root CA.

      • Miixms
      • 2 days ago
      • Reported - view

       you should check the github repo, the domain section doesnt seem to get checked..

      91 issues open at the filters section

    • TheAliDev
    • 2 days ago
    • Reported - view

    I never thinked that NextDNS staff will reply to this forum 

    I know why

    Because your blockpage is good feature

    But there is no need for it i think so

    Even this forum grabbed enough audience that doesn't like their blockpage

    Can you do something about your self signed certificate

    You can even use let's encrypted or any other public ssl

    Your ssl even allows unencrypted trackers to watch us

    I really can't explain situation here

      • NextDNs
      • 2 days ago
      • Reported - view

       you can’t use a public cert to generate certificates for domains you don’t own, which is what the blockpage feature is about. There is no way around a root CA for this feature unfortunately. 

      I don’t understand your claim about unencrypted trackers.

Content aside

  • 2 Likes
  • 2 days agoLast active
  • 15Replies
  • 347Views
  • 7 Following