0

NextDNS and iCloud private relay

Before nextdns would block with private relay enabled, after upgrading to IOS 15.4 and Monterey 12.3 I noticed it does not any more. Anyone else notice this?

13 replies

null
    • iamtheanon
    • 2 yrs ago
    • Reported - view

    It happens to me as well. Currently, I have just disabled the Private Relay since I value blocking  tracking much more rather than the Private Relay features...

    • Shawn_Blavesciunas
    • 2 yrs ago
    • Reported - view

    It appears the config profile for macOS Monterey 12.3 does not work anymore. I have uninstalled and reinstalled it. But under network it just stays as inactive and will change to running 

    • Shawn_Blavesciunas
    • 2 yrs ago
    • Reported - view

    NextDNS support  any insight?

    • Shawn_Blavesciunas
    • 2 yrs ago
    • Reported - view

    As for now I just removed the Mac profile and IOS profiles. Seemed to be causing browsing issues on IOS devices. Where on MacOS the service would not run anymore on 2 different Macs. Reinstalled Profiles, deleted my config on NextDNS and started new. Not sure if Private Relay changed or NextDNS. I seen comments awhile back they were working with apple, but since then no news. 

    • JasonMatthew_Pridgen
    • 2 yrs ago
    • Reported - view

    I’m running an upcoming version of MacOS (and iOS) to be released later.  I’ve turned private relay off. I checked last night after upgrading my operating systems to see if NextDNS worked and showed the green light that it was configured. 
    It is my understanding that while Private Rely is On then 1.1.1.1 will handle Apple’s DNS duties for their OS’s. 

      • Shawn_Blavesciunas
      • 2 yrs ago
      • Reported - view

      Jason-Matthew  if you have private relay disabled everything should work. But before when you had private relay enabled the system seemed to do a double check, I still can see the items in the logs but not being blocked. Also with no replies from nextdns on the issues or any previous private relay posts I’m assuming apple has quit working with them on a fix. Also there are more partners than just cloudfare (1.1.1.1) involved in private relay I believe. Fastly and Akamai are the other two I think.

    • tidyadd1122
    • 2 yrs ago
    • Reported - view

    running fastest MacOS and never seen issue with NextDNS and Private relay.

    How do I know if both are running ?

    I see 'This device is currently using ”iCloud Private Relay” as DNS resolver.' from NextDNS page.

    I am basically running NextDNS Cli from router and NextDNS app on Mac and of course  NextDNS Cli is not doing anything due to app running on MacOS. If I use private relay without App running on MacOS, it does not filter anything.

    I see Cloudflare as my private relay DNS server.

      • jond_7
      • 1 yr ago
      • Reported - view

      tidyadd1122 Can you elaborate on where you see "'This device is currently using 'iCloud Private Relay' as DNS resolver."?

      I've never seen this on the NextDNS Setup page from iPhone, iPad, or Mac despite using Private Relay on most devices. I just checked the settings again.

      Oddly, I found this discussion troubleshooting one iPad that seemed NOT to be making requests through my LAN's NextDNS CLI. When I turned off Private Relay, it's DNS requests started appearing in the logs. Meanwhile my other devices (several iPhones and Macs) have PR enabled and appear in NextDNS logs as expected.... ??

    • Webscientists
    • 1 yr ago
    • Reported - view

    Weird, that some of the traffic gets blocked on private relay with NextDNS

    • Mike.33
    • 3 mths ago
    • Reported - view

    I am having the same issue. Switching off Private Relay allows NextDNS to work in Safari.

    https://help.nextdns.io/t/g9yxv3l/this-device-is-not-using-nextdns

      • Mike.33
      • 3 mths ago
      • Reported - view

      If I change my Apple Privacy “Hide IP address” setting to “trackers only” instead of “trackers and websites” it works. Weird.

      • Will_Tisdale
      • 2 mths ago
      • Reported - view

       It's not weird - it's how it works.

      NextDNS needs to know the IP address that is connecting to the setup webpage in order to identify whether that device is using NextDNS or not. If the connecting IP address is changed to an anonymised one (which is what private relay does), the setup page cannot establish that and it will say that the device isn't using NextDNS. Changing the setting to trackers only, as you have, allows the IP to be sent and a correct status to be shown.

      • Mike.33
      • 2 mths ago
      • Reported - view

       thanks Will. Yeah I see what you mean. What’s really strange is after I switched it back to trackers and websites, the NextDNS website still reported it’s working. It was also always reporting it working on my iPhone which is also using private relay. I’m not sure why it sometimes says it’s working and other times says it’s not, when the settings are the same. ¯

Content aside

  • 2 mths agoLast active
  • 13Replies
  • 3449Views
  • 10 Following