0

Block page enabled, but returns 0.0.0.0

Trying to workaround the BigSur issue with 0.0.0.0 delay and enabled to the "Block page" feature.

NextDNS returns block page IP for the domains in deny list, but still returns 0.0.0.0 for domains in the NextDNS-managed block lists (ads and so on). For example fls-na.amazon.com .

Is it expected?

6 replies

null
    • NextDNs
    • 2 yrs ago
    • Reported - view

    Some domains have blockpage disabled because they are known to create issues. This is all handled for you so you don't have to bother.

    • Stas
    • 2 yrs ago
    • Reported - view

    thanks for fast reply! Any ideas how to deal with the 0.0.0.0 delay in this case?

    Do you plan to change this behavior and have block page IP get returned to all blocked queries? Or return NXDOMAIN (as feature).

    As a work-around I had to remove all blocklists on the "Privacy" page.

    • Stas
    • 2 yrs ago
    • Reported - view

    would like to follow up on this topic. Do you plan to change the behavior for the blocked domains in the 'privacy' or 'security' group and return the blocked page IP or NXDOMAIN?

    For now I had to switch off those features, otherwise page load in Chrome\Firefox is incredibly slow

      • Chris.6
      • 2 yrs ago
      • Reported - view

      Stas This only happens when using a browser other than Safari, while having a network extension like Little Snitch or LuLu active. It's supposed to be fixed in macOS 12 beta, but meanwhile you could try using Safari or deactivate any network extension.

    • NextDNs
    • 2 yrs ago
    • Reported - view

    There should not be any delay with 0.0.0.0. What is you platform/OS?

      • Chris.6
      • 2 yrs ago
      • Reported - view

      NextDNS This is a bug in Bug Sur that has been written about on Reddit almost a year ago (only happens with 0.0.0.0, not NXDOMAIN).

      But since noone seems to send feedback to Apple (or Apple just doesn't care about fixing bugs any more), this is still a thing. After sending Apple feedback in August and pointing an Apple developer to it via Twitter, they seem to have looked at it and replied that this is fixed in macOS 12 beta. If someone can test this, I'd be happy to know (scared to run the beta myself). 

Login to reply

Content aside

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