ThisCalculator

Everyday

NextDNS to Control D Migration Guide

Updated · Standard formula, shown below

NextDNS to Control D Migration Guide

Switching from NextDNS to Control D lets you keep your custom filtering rules, blocklists, and analytics while moving to a different DNS provider. This guide walks you through exporting your settings from NextDNS, importing them into Control D, and updating your devices so you don’t lose your carefully tuned configuration.

What You’ll Need

  • An active NextDNS account with the settings you want to migrate
  • A Control D account (free or paid) – sign up at controld.com
  • Access to your router’s admin panel or the devices you use for DNS (phone, computer, etc.)
  • A text editor (like Notepad or VS Code) to review exported files

Step-by-Step

  1. Export your NextDNS configuration. Log in to your NextDNS dashboard. Go to the configuration you want to migrate (e.g., “Homeâ€�). Click the three-dot menu next to the configuration name and select “Export.â€� You’ll get a JSON file containing your blocklists, allowlists, rules, and other settings. Save it somewhere safe.
  2. Review the exported file. Open the JSON file in a text editor. Look for sections like blocklists, allowlists, rules, and settings. Note the blocklist names (e.g., “OISD Fullâ€�) and any custom rules you’ve added. This helps you know what to recreate in Control D.
  3. Create your Control D configuration. Log in to Control D and go to “Configurations.â€� Click “New Configurationâ€� and give it a name (e.g., “Homeâ€�). You’ll see options for DNS filtering, blocklists, and rules.
  4. Recreate your blocklists. In Control D, navigate to “Blocklistsâ€� (under the configuration). Click “Add Blocklistâ€� and search for the same lists you used in NextDNS. Common ones like OISD, Energized, and AdGuard DNS are available. If a list isn’t found, you can add it via a custom URL (see Tips). Add all the lists you had.
  5. Recreate your allowlists. In NextDNS, your allowlist is a list of domains you’ve whitelisted. In Control D, go to “Allowlistâ€� and add those same domains. You can copy them from the exported JSON (look for allowlist array).
  6. Recreate custom rules. NextDNS rules (e.g., block a specific domain, redirect) are in the rules section of the JSON. Control D uses a similar rule engine. Go to “Rules� in Control D and recreate each rule. For example, a NextDNS rule like example.com with action “Block� becomes a Control D rule with the same domain and action.
  7. Set up parental controls and privacy settings. If you used NextDNS’s parental controls (like blocking adult content) or privacy features (like blocking trackers), replicate them in Control D’s “Filteringâ€� or “Privacyâ€� sections. This includes toggles for malware, phishing, and ads.
  8. Copy your DNS server addresses. In Control D, go to “Setupâ€� and note your new DNS server addresses (e.g., polo.control-d.com or a dedicated IP). You’ll replace NextDNS’s addresses with these.
  9. Update your router or devices. Replace the NextDNS DNS addresses with Control D’s. On a router, find the DHCP/DNS settings and enter the Control D addresses. On individual devices, go to network settings and change the DNS. Make sure to remove any NextDNS-specific apps or profiles.
  10. Test your migration. After updating, visit a site that should be blocked (based on your rules) to confirm filtering works. Also check that allowed sites load fine. Use Control D’s “Logsâ€� to see queries and verify the filtering is active.

Common Mistakes

  • Forgetting to export the right configuration. If you have multiple NextDNS configs, make sure you export the one you actually use.
  • Assuming blocklists are identical. Blocklist names may differ slightly between providers. Always verify the list content matches (e.g., OISD Full is the same, but “No Adsâ€� might be different).
  • Missing custom rules. The export file includes rules, but they’re easy to overlook. Double-check that every rule is recreated in Control D.
  • Not updating all devices. If you only change your router, but your phone uses a NextDNS profile, the phone will still use NextDNS. Update every device or remove old profiles.
  • Ignoring DNS cache. After switching, your devices may still have cached DNS results. Clear the cache or wait for it to expire (usually a few minutes).

Tips

  • Use the same blocklist URLs. NextDNS lets you add custom blocklists via URL. If a list isn’t in Control D’s catalog, you can add it manually using the same URL (e.g., from a GitHub repository).
  • Export your NextDNS logs for reference. If you want to keep your analytics history, export your logs from NextDNS before you stop using it. Control D won’t have that history.
  • Start with a test configuration. Create a separate Control D config with just a few blocklists to test the migration process before committing to the full setup.
  • Use Control D’s import feature (if available). Some providers offer an import tool for NextDNS JSON files. Check Control D’s documentation – if it exists, it saves time.
  • Keep your NextDNS account active for a week. This gives you a fallback if you miss something. You can always go back.

Troubleshooting

  • DNS not working after switch. Check that you entered the correct Control D server addresses. Try using a public DNS like 1.1.1.1 to see if the issue is with Control D. Also, ensure your router hasn’t cached old DNS settings – reboot the router.
  • Some sites are blocked that shouldn’t be. This likely means a blocklist is too aggressive. Check Control D’s logs to see which list blocked the site, then add an allow rule for that domain.
  • Certain rules aren’t applying. Verify that your rules are in the correct order (rules are evaluated top-down). Also, ensure the rule syntax matches Control D’s format – you may need to adjust from NextDNS’s syntax.
  • Can’t find a blocklist in Control D. If a list isn’t in the catalog, use the “Customâ€� option and paste the raw URL of the blocklist (e.g., from the NextDNS export or the list’s official source).
  • Devices still show NextDNS as the DNS. This happens if you have a NextDNS profile installed. Remove it from your device’s settings or uninstall the app. Also check for leftover VPN profiles.

Frequently Asked Questions

Can I import my NextDNS JSON directly into Control D?

Control D does not have a one-click import for NextDNS JSON files. You’ll need to manually recreate your settings, but the process is straightforward using the steps above.

Will my custom blocklists from NextDNS work in Control D?

Yes, if the blocklist is available as a URL, you can add it to Control D as a custom list. Ensure the URL is accessible and the format is compatible (plain text, one domain per line).

Do I need to change DNS settings on every device?

If you set DNS at the router level, all devices on that network will use Control D automatically. But if you have device-specific settings (like a NextDNS app), you must update those individually.

What happens to my NextDNS analytics after I switch?

Your NextDNS logs and analytics will remain in your NextDNS account until you delete it, but you won’t get new data. Control D has its own analytics that will start collecting once you switch.

Can I keep my NextDNS account as a backup?

Yes, you can keep your NextDNS account active without using it. Just make sure to update your devices to use Control D, otherwise they’ll continue using NextDNS.

Is there a way to migrate my allowlist automatically?

There’s no automatic way. You’ll need to copy the domains from your NextDNS export and paste them into Control D’s allowlist. It’s a manual step but quick if you have a small list.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.