Fleet Service Point - BlueCat DNS Edge

From the Fleet Service Point page, you can download the required Fleet Service Point files to provision your Fleet Service Point to your VMware environment, AWS environment, Azure environment, GCP environment, or Cisco ENCS devices.

If you are provisioning on VMware, you can download the OVA image of the Fleet Service Point and the associated checksum file. The OVA image can be reused to provision multiple Fleet Service Points in your environment; however, you can only apply one Fleet Service Point configuration per Fleet Service Point image. Once you have created the Fleet Service Point within the Edge Cloud, you can download the base64-encoded configuration JSON file that will be used to register the Edge Fleet Service Point to the DNS Edge Cloud. Once the Edge Fleet Service Point has registered in the DNS Edge Cloud, you can provision the DNS resolver service.

If you are provisioning on AWS, Azure, or GCP, you must create the Fleet Service Point through the Edge Cloud. Once created, you can are presented with a base64-encoded configuration text file that contains information that will be used to register the Edge Fleet Service Point to the DNS Edge Cloud. Once the Edge Fleet Service Point has been provisioned on AWS, Azure, or GCP and registered in the DNS Edge Cloud, you can deploy the DNS resolver service.

If you are provisioning on a Cisco ENCS device, you can download the tarball image of the Fleet Service Point and the associated checksum file. The tarball image can be reused to provision multiple Fleet Service Points on Cisco ENCS devices; however, you can only apply one Fleet Service Point configuration per Fleet Service Point image. Once you have created the Fleet Service Point within the Edge Cloud, you can are presented with the registration key and registration endpoint information that will be used to register the Edge Fleet Service Point to the DNS Edge Cloud. Once the Edge Fleet Service Point has registered in the DNS Edge Cloud, you can deploy the DNS resolver service.

Attention: The registration key and registration endpoint of the Fleet Service Point can only be retrieved at this point and cannot be recovered later. These values are required when configuring the VM on Cisco ENCS.

Once you have provisioned the Fleet Service Point with a registration key and registration endpoint, the values are invalidated and cannot be used again to provision another Fleet Service Point.

In the top navigation bar, click and select Fleet Service Points. A new tab opens with the Fleet Service Points overview page.

The Fleet Service Points overview page shows a list of Edge Fleet Service Points that were previously provisioned. You can click the name of an Edge Fleet Service Point to display additional information.

For more information on provisioning Fleet Service Points on VMware, AWS, Azure, GCP, or Cisco ENCS devices, refer to the following sections:

Warning: The Fleet Service Point introduces the ability to easily access the Fleet Service Point VM through SSH connections. Do not modify any files or perform actions within the file system unless instructed to by a member of BlueCat. This includes the following actions:

Installing non-standard Debian packages
Manually updating or deleting any pre-installed packages
Modifying any files

Failing to abstain from performing these actions can result in unexpected behavior and errors when operating the Fleet Service Point.