NextDNS not working with JamfNow
Hi,
I posted this in the community, but did not get any replies. Would truly appreciate if you can help me fix the problem (I have already invested more than 10 hours and the Jamf support team referred me to you given that the issue seems to lie in the configuration profile itself and is pushed to the device):
I’ve tried everything to get NextDNS to work reliably on my child’s supervised iPad via Jamf Now, but I’m stuck.
Here's what I've done so far:
- I created a NextDNS configuration profile and installed it on the iPad using Jamf Now
- The iPad is properly enrolled and supervised
- The DNS proxy payload appears correctly under Settings → VPN & Device Management
- However: The iPad still shows the message: “This device is not using NextDNS”
- In DNS settings, NextDNS Proxy (with correct ID) is visible but marked as “Invalid”
- I tried:
- Downloading a new mobileconfig from NextDNS
- Creating a .plist file via iMazing Profile Editor
- Installing the official NextDNS iOS App – but it always shows as “disabled”, even after enabling it
- Interestingly, when I install the classic NextDNS profile (not the DNS Proxy type), NextDNS works and shows as active – but this profile doesn’t link to my configuration ID, so the custom settings (like filters and logs) don’t apply across all networks
What I’m trying to achieve:
- Enforce NextDNS protection using my profile ID (6ac41d) on a supervised iPad
- Ensure it works in all networks (Wi-Fi, hotspots, etc.)
- Prevent any bypass (app deletion, DNS/VPN changes are restricted via Jamf Now)
Does anyone have an idea how to fix this? I’ve already invested hours troubleshooting this and would really appreciate any advice or working solutions from the community!
Reply
Content aside
- 6 days agoLast active
- 12Views
-
1
Following