DNSFilter

DNSFilter protects your customers’ DNS traffic and blocks threats and unwanted content. Connect it once with an API key from your MSP organization, and Neo agents can report on and work in every customer organization under it.

​

What Neo can do with DNSFilter

• Build the security section of a quarterly business review: the threats DNSFilter blocked for the customer, their categories and trend, and the users and devices it protected
• Unblock a site from a ticket: check the domain’s category and recent blocks, find the customer’s policy, and, once approved, add the domain to its allow list
• Add a phishing domain to a customer’s block list
• Read and decide end users’ unblock requests
• Check whether a computer’s roaming client is protected and online, and which policy filters it
• Read networks, policies, block pages and report schedules, and your customer organizations

​

Each ticket stays with its customer

One DNSFilter key from your MSP organization reaches every customer organization under it. On a ticket that names a company, Neo sends a call only for the organization the ticket’s company is mapped to. A change to one policy, network or roaming client names that organization, and Neo first reads the record to confirm it belongs to that customer. A global policy shared by several customers is changed only outside a ticket run, such as from a chat with Neo or by a technician.

​

Allow and block lists ask first by default

Allowing a domain lets users reach a site the customer’s policy blocks, so the Helpdesk and IT Admin profiles ask a technician before any change to a policy or an unblock request. Before it allows a site, the agent checks it and never allows a domain DNSFilter puts in a security category.

​

Your organizations are mapped to companies

Neo matches your DNSFilter customer organizations to the companies in your PSA and keeps the mapping on the DNSFilter card’s Organization Mapping tab, refreshed on each PSA metadata sync. Your own MSP organization and canceled organizations are left out. 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 DNSFilter 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 DNSFilter API for the permission groups.

​

Next steps