Investigate a Domain
Check recent DNS queries for [domain] and its matching lists. Explain the blocking reason.
Leina connects to Pi-hole to help you investigate blocked domains and review DNS activity. Ask in your team chat. Leina does the work and brings back the result.
Connect Pi-hole, choose what to share, and hand off your first task.
You
Check why the sample-news site is blocked. Read its recent queries and matching lists.
Leina
The domain matches a blocking list. I’ve recorded the match and the recent query outcome.
Pi-hole · Example
sample-news · DNS review
The blocking reason is ready for review.
A Pi-hole AI agent can trace a blocked domain, review DNS activity, or pause blocking for a duration you specify.
You specify the source and the destination. Leina uses the content available to your connection and returns the result for you to review.
Pi-hole filters DNS requests to block unwanted domains.
Choose the domain and time period.
Read DNS queries and matching list entries.
See the evidence before changing blocking.
Copy a prompt, add your details, and send it to Leina in your connected team chat.
Check recent DNS queries for [domain] and its matching lists. Explain the blocking reason.
Review Pi-hole DNS activity and upstream response times. Summarize anything that needs attention.
Pause DNS blocking for [duration], then check the resulting blocking status.
Your next Pi-hole task can start with a message.
Tell Leina what you need in your team chat. Include the source, destination, and expected result.
Connect the tools involved and give Leina access to the content it needs.
Share the source material, say where the result belongs, and describe what you need.
Review the result and any changes in the connected app.
Hand off these everyday tasks to your AI employee.
Fetch the Pi-hole activity overview: total and blocked queries, blocked query percentage, unique clients and domains, and the blocking and gravity list status.
Fetch whether Pi-hole DNS blocking is currently enabled, disabled, failed, or unknown.
Enable or disable Pi-hole DNS blocking, optionally for a limited time after which the opposite mode is restored automatically.
Query the Pi-hole DNS log with optional filters. By default returns the most recent queries; each response exposes a cursor for the next chunk.
Fetch the number of queries of each DNS query type that Pi-hole has seen.
Fetch the domains Pi-hole has handled the most, optionally limited to blocked ones.
Fetch the clients that have queried Pi-hole the most, optionally limited to blocked ones.
Fetch the domains most recently blocked by Pi-hole.
Fetch metrics about Pi-hole's DNS upstream destinations, including response times.
Fetch the Pi-hole activity graph data: query totals over time with cached, blocked, and forwarded splits.
Search whether a domain appears in Pi-hole's allowlists, blocklists, or gravity lists, to understand why it is blocked or allowed.
Fetch the current Pi-hole configuration, such as DNS settings, privacy level, and API settings.
Change part of the Pi-hole configuration, for example DNS upstreams, the privacy level, or API settings. The provided fields are merged into the current configuration.
Run the Pi-hole gravity update to refresh the blocklists. The instance streams the gravity log; the action reports a best-effort status from the log plus the tail of the stream.
Restart Pi-hole's DNS server and reload its DNS configuration.
Flush the Pi-hole DNS query log.
List all Pi-hole groups and their memberships.
Create one or more Pi-hole groups, optionally with a comment and enabled state.
Update one Pi-hole group: rename it, or change its comment or enabled state.
Delete one Pi-hole group by name.
List the Pi-hole allowlists and blocklists (subscription lists).
Add one or more allowlist or blocklist entries (addresses) to Pi-hole.
Update one Pi-hole list: change its comment, enabled state, or group memberships.
Delete one Pi-hole allowlist or blocklist entry by address.
List the individual Pi-hole domain entries, optionally restricted to one type or kind.
Add one or more allow or deny domain entries to Pi-hole, either exact or as regular expressions.
Update one Pi-hole domain entry: change its comment, enabled state, or group memberships.
Delete one Pi-hole allow or deny domain entry.
List all Pi-hole clients and their group memberships.
Register one or more Pi-hole clients identified by IP address, MAC address, hostname, or interface.
Update one Pi-hole client's comment or group memberships.
Delete one Pi-hole client entry by identifier.
Delete multiple Pi-hole groups by name in one request. Reports deleted=false when none of the groups exist.
Delete multiple Pi-hole allowlist or blocklist entries in one request. Reports deleted=false when none of the entries exist.
Delete multiple Pi-hole domain entries in one request. Reports deleted=false when none of the entries exist.
Delete multiple Pi-hole client entries in one request. Reports deleted=false when none of the clients exist.
Fetch the currently active DHCP leases assigned by the Pi-hole DHCP server.
Fetch the devices seen on the local network by Pi-hole.
Create a complete Pi-hole teleporter backup archive (teleporter.zip) with all settings, lists, and clients.
Restore a Pi-hole teleporter backup archive (a previously exported teleporter.zip) to this instance.
Connect the Apps your work depends on, and give Leina the context to carry the task forward.
Hand off a task while your team is discussing it. Leina uses your connected tools and brings the result back to the conversation.
See How Leina Works in SlackThe domain matches a blocking list. I’ve recorded the match and the recent query outcome.
No. This connection needs a publicly reachable Pi-hole instance.
Yes. When the timer ends, Pi-hole switches to the opposite blocking mode.
Start with one task you already need to do. Tell Leina what a finished result should look like.
Connect Pi-hole, choose what to share, and hand off your first task.