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 reflect the branded and legacy Whitelabel agent. Here’s what the names mean:
- DNS Agent → This is the unbranded (legacy Whitelabel) DNSFilter Roaming Client.
- DNSFilter Agent → This is the standard branded Roaming Client.
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.
For MSP accounts created before September 15, 2026 with Whitelabel enabled, the app and service appear as DNS Agent on Windows and macOS. New MSP accounts use Branding instead — see MSP Branding for the current setup path.
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
Iniciar sesión para dejar un comentario.
Comentarios
1 comentario