In this article

Sites connect two key elements to Roaming Clients:

• Filtering policies—how DNSFilter protects your network from internet threats
• DNS queries—how billing is tracked

✍️ Every Roaming Client must be associated with a Site during the deployment process.

If you intend to only deploy a Roaming Client without redirecting DNS traffic at the local network level (deploying DNS Forwarding), remember that an IP address isn't necessary while setting up the Site.

When working with multiple Sites, choose the best Site for the end user's behavior or your billing needs:

• If the device is normally at a specific location (i.e.: Office, School, etc.), use that Site
• If the end user is primarily remote and typically isn't local on a specific Site, the choice becomes irrelevant except for billing purposes

Change the Site association at any point by editing the Roaming Client settings.