I just updated to Monterey Beta and got a message saying “Your system settings are in compatible with Private Relay” so maybe that’s a step in the right direction. Running NextDns CLI.

Also running private relay but I’m not seeing any issue with things being bypassed at this point?  Does the bypass function when creating a mobileconfig actually bypass this, or? Just wondering if perhaps I should be having private relay turned off? I know it’s still in beta obviously.

Hi, Just to add a little extra info to this topic. I am running iPad OS 15 Beta 5 on an iPad Pro and when using Private Relay this bypasses NextDNS on the iPad too. Disabling Private Relay allows a stable connection to NextDNS.

Can someone try this with the new beta?

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.

is there any news?

Just an update, iOS 15.2 beta does not change anything. I continue to use NextDNS with Private Relay enabled without any issues, but the caveats mentioned by NextDNS above still apply.