controld_skill

Overview

This skill manages the Control D DNS filtering service via its API. It provides programmatic control over DNS profiles, devices, filters, services, custom rules, analytics, and organization provisioning. Use it to automate DNS blocking, device onboarding, and network diagnostics at scale.

How this skill works

Authenticate with a Control D API token and call the REST endpoints at https://api.controld.com. The skill exposes endpoints for profiles, devices, filters, services, custom rules, proxies, analytics, IP access, and organization management. Commands map to create/read/update/delete operations and common workflows like cloning profiles, setting service actions, and provisioning device codes.

When to use it

• Automating profile creation, cloning, and bulk updates across many endpoints.
• Onboarding and configuring devices or routers with specific DNS profiles programmatically.
• Implementing custom domain block/bypass rules or applying service-level actions.
• Collecting device analytics or configuring logging and storage for audits.
• Managing organization-level settings, sub-organizations, and provisioning codes for MSPs.

Best practices

• Store API tokens in a secure environment variable and restrict tokens by allowed IPs for automation hosts.
• Use read-only tokens for reporting and write tokens only where modifications are required.
• Test changes on a cloned profile before applying to production devices.
• Use provisioning codes and RMM integration for mass deployment to endpoints.
• Limit analytics retention and choose appropriate storage regions to control costs and data locality.

Example use cases

• Create a family profile that blocks advertising and adult content, then assign it to kids' devices.
• Clone a corporate default profile, adjust service bypass rules for a specific office, and roll it out to that office's routers.
• Add custom blocking rules for a set of malicious hostnames discovered in threat feeds.
• Generate provisioning codes for a new client and bulk-deploy the ctrld daemon via RMM.
• Enable full analytics for a troubleshooting device and pull activity queries for a specific date range.