BloxOne Threat Defense Cloud introduces a new workflow that streamlines the DNS forwarding proxy deployment process. You no longer need to pre-provision hosts through the Cloud Services Portal, nor do you need to copy API keys to establish host connection when configuring DNS forwarding proxies on bare-metal containers or virtual machines.
Virtual Appliances
Before you configure a virtual machine as a DNS forwarding proxy, you must first create a join token and use it to authenticate the host, so BloxOne Threat Defense Cloud can establish a connection to the host. For information about join tokens and how to manage them, see /wiki/spaces/InfrastructureDRAFT/pages/82150299. Once you set up the virtual appliance using a valid join token, a connection to BloxOne Threat Defense Cloud is established, and the host status changes to Active (if the host and all the services running on it are functioning properly). The host is now a fully manageable device, and you can manage it through the Cloud Services Portal.
The following diagram illustrates the provisioning process for DNS forwarding proxies deployed on virtual machines:
You can view all connected and disconnected proxies on the Manage > Infrastructure > Hosts page of Cloud Services Portal, which allows you to manage all your devices. The portal gives you a collective view of all of your devices in the network, including the device's current status.
For more information, see BloxOne Infrastructure.