adguard_skill

Overview

This skill controls AdGuard Home DNS filtering via its HTTP API. It lets you check domain filtering status, add or remove block/allow rules, view statistics, toggle protection, and clear the DNS cache from the command line. Configuration is via environment variables or a small config file and requires AdGuard admin credentials.

How this skill works

The skill sends authenticated REST API requests to your AdGuard Home instance to inspect and modify DNS filtering state. It can query whether a domain is blocked, add exception or block rules, fetch protection and query statistics, toggle the protection flag, and clear the DNS cache to force rule updates. Authentication relies on an admin username and password kept out of config files when possible.

When to use it

• When you need to verify if a domain is blocked or allowed by your DNS filters.
• When you want to add a one-off allow or block rule without using the web UI.
• When you need to view DNS query statistics and the current protection state.
• When you must temporarily disable DNS filtering for troubleshooting or testing.
• When rule changes aren’t taking effect and you need to clear the DNS cache immediately.

Best practices

• Store the admin password in ADGUARD_PASSWORD environment variable, not in plain files.
• Set ADGUARD_URL and ADGUARD_USERNAME in your shell profile for persistent access.
• Use allow (whitelist) rules sparingly so blocklists remain effective.
• Clear the DNS cache after adding/removing rules to apply changes right away.
• Run batch operations carefully; test on a single domain before scripting bulk changes.

Example use cases

• Check whether ads.google.com is currently blocked before troubleshooting a site.
• Add an allow rule for a business site that a blocklist is breaking.
• Block a known malware domain across the network by adding a custom rule.
• Temporarily disable DNS protection to isolate a connectivity problem.
• Clear the AdGuard DNS cache after updating blocklists or exception rules.