
Apple Private Relay
I'm not sure that this is a bug and there may not be a work around for it. Running the beta for macOS Monterey and when Private Relay is turned on it bypasses NextDNS and uses Cloudflare.
-
The current behavior and most likely the behavior of the release is that iOS (and macOS) when Private Relay is enable is using NextDNS only to check if a domain is blocked, but uses the Private Relay’s DNS (Cloudflare, Akamai…) for the actual DNS resolution (all DNS request are duplicated).
This will create different problems:
* Our status page won’t work properly
* Blocking won’t work at all if the blockpage feature is enabled
* Rewrites won’t work and thus safe search and youtube restricted mode won’t be enforced by extension
* DNS leak tests will show another resolver than NextDNS
We worked with Apple on this and agreed on a better solution, but they could not implement it on time for the release. We hope the correct behavior will be implemented in the next dot release.
In the meantime, we do not recommend using both Private Relay together with NextDNS.
-
NextDNS said:
Blocking won’t work at all if the blockpage feature is enabledSo blocking works without enabled blockpage?
-
Hi there, another question: I enabled private relay and nextdns did not work anymore. then i deactivated private relay and nextdns should be working properly again... but... it doesn't. it does not block the ads anymore although the nextdns page says everything is working fine... any ideas how to fix this?