1

iCloud Private Relay interoperability broken by the “FASTLY” servers.

When NextDNS is used with iCloud private relay, it normally works just fine, showing normal functionality, etc. 

but for some reason, even if you’re using a signed configuration profile, even if that profile is set up for the device it’s installed on, even if you’re using bootstrapped IPs, etc. when private relay decides to connect to “FASTLY” the interoperability breaks. The only temporary fix is to reboot and hope private relay finds a different server or to fully re-install the configuration profile. This needs to be fixed ASAP. 

4 replies

null
    • NextDNs
    • 2 wk ago
    • Reported - view

    There is nothing we could do about this other than not recommending to use private relay with a DNS filter. Those two features don’t play well together.

      • silent
      • 2 wk ago
      • Reported - view

       it works fine normally, that’s the only iCloud private relay server that it has issues with, perhaps the fastly server is newer? 
       

      also the current only fix is to re-install the profile. 

    • Paulo_Emilio
    • 2 wk ago
    • Reported - view

    When you activate and use iCloud Private Relay, Safari bypasses the DNS Profile configured with NextDNS and uses Akamai or CloudFlare for DNS security. This is iOS design. You can use another browser, which will use the DNS Profile and iCloud Private Relay, in Safari, for redundancy.

      • silent
      • 2 wk ago
      • Reported - view

       when it’s using those, and installed via a config profile, it will work properly. The issue seems to only come up intermittently, and only with the fastly servers. 

Login to reply

Content aside

  • 1 Likes
  • 2 wk agoLast active
  • 4Replies
  • 109Views
  • 4 Following