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.
-
We know. It is in discussion with Apple.
-
NextDNS for reference: https://youtu.be/hTdhLgsBkj8?t=1731
https://youtu.be/hTdhLgsBkj8?t=1731 -
Very helpful. I hope to use NextDns in Monterey whether through Private Relay or separately.
-
-
Thanks!
-
Ray and Brenda Horn did you try new beta 2?
-
DynamicNotSlow Not yet. Will be trying that today.
-
-
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.
-
NextDNS said:
Blocking won’t work at all if the blockpage feature is enabledSo blocking works without enabled blockpage?
-
DynamicNotSlow It does for me, yes.
-
Chris same for me. It’s sad nobody from Team answer that question but community member.
i also figure it out by myself in that time -
DynamicNotSlow just an FYI and a thank you. I saw you follow my iOS 15.1 RC bug so I read this thread. By turning off Block Page, it fixed my issue. Doesn’t explain why the RC broke things, but at least it’s working properly again.
-
-
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.
-
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?
-
David Wachter it works. Read above comments.
you need to disable block page in NextDNS -
DynamicNotSlow thanks!
-
-
When I use the NextDNS app on macOS my real ipv4 address is leaked. On IPv6 it is part of private relay. Anyone else seen this or is it a known bug?
