Internal Networks allows to you manage your Umbrella policy for subnets of computers based on the internal IP addresses of your network.
After an Umbrella virtual appliance (VA) has been deployed, an Internal Networks identity can be configured. To set this up, drop one of our lightweight VAs into your network, direct your DNS traffic through it, and start mapping your network based on specific internal IP addresses and/or subnets.
The purpose of the Internal Networks identity is to define a subnet that's non-routable (or RFC1918 compliant) as an identity to which you can apply a DNS policy. To create an Internal Networks identity, define a subnet that's non-routable (or RFC 1918 compliant) as an identity to which you can apply a policy. For example, if your Internal Network is defined as 192.168.0/24, any computer, tablet, or device with an IP on that subnet would receive the filtering policy defined for it whenever it made a request to access the Internet.
From there you can begin to build multiples sites if you have more than one physical location or if you have more than one Internal Network to configure.
The Umbrella VA will have your DNS traffic pointed to it for this configuration and anything identified as coming from the networks you've defined will have the policies applied.
For more information about whether you should be using sites in your network, see Sites and Internal Networks.
The following steps are required to set up an internal network:
Note: These steps assume you have set up a VA. If you have not yet done so, provision VAs before you continue. For more information, see the Virtual Appliance Setup Guide.
Introduction > Provision a Subnet for Your Virtual Appliance
Updated about a year ago