MacOS Profile ignores NextDNS in public WiFi, while iOS doesn't - why?

Hi everyone,

I've noticed an inconsistency with NextDNS profiles between my iOS and MacOS devices that should be addressed.

The Issue:
I'm using (almost) identical mobileconfig profiles on both my iPhone and MacBook. While my iPhone keeps using NextDNS in public WiFi networks, my MacBook switches to the network's DNS servers assigned by DHCP in some cases. The NextDNS app works fine on MacOS, but I'd prefer using the profile solution.

Technical Details:
Running test.nextdns.io shows:
- iPhone: "status": "ok", using DoH as configured
- MacBook: "status": "unconfigured", using DNS server of the respective network.

Both devices are using the same profile configuration (DoH, User scope). The only difference is that MacOS seems to let DHCP settings override the profile settings, while iOS properly enforces them.

While I can use the NextDNS app as a workaround, I believe the profile should work the same way on both platforms. Could the MacOS profile implementation be updated to match the iOS behavior?

Let me know if you need any additional information from my setup.