Skip to main content

Sites

A site represents a location or logical grouping — a head office, a branch, a data center, or a set of VLANs. Sites are how you keep one location's DNS/DHCP off another location's servers within the same tenant.

Open it from Infrastructure → Sites.

Why sites matter​

Sites are the unit of scoping. You assign zones, scopes, subnets, and agents to a site, and:

An agent receives only the configuration for its site, plus anything marked global (assigned to no site).

So an agent at the Branch site serves Branch zones and scopes and global resources — never HQ-only resources. This lets a single tenant run many independent locations cleanly.

Create a site​

  1. On the Sites page, create a new site.
  2. Give it a name (e.g. Main Office) and a region (e.g. local, us-east).
  3. Optionally nest it under a parent site to build a hierarchy (region → city → building).
  4. Save.

The Startup Wizard can also create your first site as part of building a network.

Assign resources to a site​

You assign resources from their own lists using the site badge (which shows global until assigned):

  • DNS zones — site badge on the Zones list.
  • DHCP scopes — site badge on the Scopes list.
  • IPAM subnets — site badge on the Subnets list (assigning a container cascades to its children; bulk mode assigns many at once).
  • Agents — set the site on the agent's row, or pick it at deploy time.

Choosing global (all agents) keeps a resource unscoped so every agent serves it — handy for shared infrastructure like a common internal domain.

Site hierarchy​

Sites can nest, which helps large or multi-region estates:

North America
 ├─ Toronto HQ
 │   ├─ Agent: hq-dns-01
 │   ├─ Zone:  corp.local (or global)
 │   └─ Scopes for HQ VLANs
 └─ Vancouver Branch
     ├─ Agent: van-dns-01
     └─ Scopes for branch VLANs

IPAM can group its tree by site, and Network Intelligence (Advisor, Risk Score) can be filtered per site — useful for focusing on one location at a time.

  • Key concepts — how sites fit with tenants and agents.
  • Agents — site-based scoping of what each agent serves.
  • MSP Guide — sites within per-client workspaces.