Explanation between the services of "DNS Agent" and "DNSFilter Agent"
, I noticed that for the majority of our endpoints, the software and service are called "DNS Agent". However, I also noticed that for some endpoints, the software and service is called "DNSFilter Agent".
was wondering if you could provide an explanation as to why the name of this application/service would be different on some devices, despite having the same version installed. Is it dependent on how the application was installed?
I'd appreciate any insight on the matter.
-
Great question, Mark Ocampo! Happy to help.
The two different names are the branded and whitelabeled agent. Here’s what the names mean:
- DNS Agent → This is the unbranded (whitelabeled) DNSFilter Roaming Client. When whitelabeling is enabled from the MSP dashboard, the app and service appear as DNS Agent on Windows and macOS.
- DNSFilter Agent → This is the standard branded Roaming Client when whitelabeling is not enabled.
If you’re seeing a mix of both across endpoints, it typically means the agent was deployed via an MDM or RMM and there was a mix-up in the installer package or deployment script used. Functionally, both clients behave the same—this is purely a branding difference.
One thing to watch for: mixed branding can sometimes result in duplicate Roaming Clients showing up in the dashboard. If that happens, we have a recommended cleanup approach documented in this Community post.
Hope that helps clarify things!
0
Please sign in to leave a comment.
Comments
1 comment