> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# ScoutDNS

> Let Neo agents research the domain review requests your users send, answer questions about each customer's roaming clients and locations, and change allow and block lists

ScoutDNS filters DNS for your customers' sites and roaming devices. Connect it once with an API key from cloud.scoutdns.com, and Neo agents can read and act across your ScoutDNS organizations.

## What Neo can do with ScoutDNS

* Research a "ScoutDNS Domain Review Request" ticket: read the query log for the domain, why ScoutDNS blocked it (a category, a threat or a list), which policy blocked it, and who else hit it, then write the findings and a recommendation on the ticket
* Allow the domain on the customer's own allow list once it is approved, and read the list back to confirm
* Answer questions in a chat with Neo about a customer: its roaming clients and whether they are online, its locations and networks, its client counts
* Read each customer's threats blocked, top blocked domains and categories, and query statistics, for a QBR or a security review
* Read and change policies, TLD filters and block pages, locations and networks, roaming clients and profiles, and customer organizations
* Get the roaming client installer for a new device, for your RMM's install script

## Each ticket stays with its customer

One ScoutDNS key reaches every organization in your account. On a ticket that names a company, Neo sends a call only for the ScoutDNS organization the ticket's company is mapped to. A call about one record (a list, a location, a network, a roaming client or a profile) names that organization, and Neo first reads the record to confirm it belongs to it. A list shared across your account, the account-wide lists, policies and console users are changed only outside a ticket run, such as from a chat with Neo.

## Some changes always ask first

Deleting an organization, a location or a network, turning filtering off (disabling a location's networks or a roaming client, uninstalling a roaming client, or a network edit that turns it off), deleting a roaming client profile, and creating or editing a log stream always wait for a technician's approval, whatever the agent's settings. Neo does not edit a roaming client profile or a log stream whose SIEM settings hold a secret: a technician changes those in ScoutDNS, so Neo never overwrites a value it cannot see.

## Your customers are mapped to companies

Neo matches your ScoutDNS organizations to the companies in your PSA and keeps the mapping on the ScoutDNS card's **Organization Mapping** tab, refreshed on each PSA metadata sync.

Matching uses the organization name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the long tail.

**A name that matches exactly one of your PSA companies, as it is or after stripping a legal-form suffix, or a match you confirm, is handed straight to your agents.** A name two of your PSA companies share, or two organizations that match one company, is left to the AI match, and an AI match waits for you on the Organization Mapping tab. Confirm or correct each there.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.

See [ScoutDNS API](https://docs.neoagent.io/agents/tools/security/scoutdns-api.md) for the permission groups.

## Next steps

> [card] [Connect ScoutDNS](https://docs.neoagent.io/integrations/scoutdns/connecting-to-neo.md)
>
> Create an API key and save it in Neo.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.