Service Point v4 - BlueCat DNS Edge

From the Service Point v4 page, you can download the required Service Point v4 files to provision your 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 Service Point v4 and the associated checksum file. The OVA image can be reused to provision multiple Service Point v4 instances in your environment; however, you can only apply one Service Point v4 configuration per image. Once you have created the Service Point v4 instance within the Edge Cloud, you can download the base64-encoded configuration JSON file that will be used to register the service point to the DNS Edge Cloud. Once the Service Point v4 instance has registered in the DNS Edge Cloud, you can deploy the DNS resolver service.

If you are provisioning on cloud environments, such as AWS, Azure, or GCP, you must create the Service Point v4 instance 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 service point to the DNS Edge Cloud. Once the Service Point v4 instance 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 Service Point v4 and the associated checksum file. The tarball image can be reused to provision multiple service point on Cisco ENCS devices; however, you can only apply one Service Point v4 configuration per image. Once you have created the Service Point v4 instance within the Edge Cloud, you can are presented with the registration key and registration endpoint information that will be used to register the service point to the DNS Edge Cloud. Once the Service Point v4 instance has registered in the DNS Edge Cloud, you can deploy the DNS resolver service.

Attention: The registration key and registration endpoint of the Service Point v4 instance 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 Service Point v4 instance with a registration key and registration endpoint, the values are invalidated and cannot be used again to provision another Service Point v4 instance.

In the top navigation bar, click and select Service Point (v4). A new tab opens with the Service Point v4 overview page.

The Service Point v4 overview page shows a list of Service Point v4 instances that were previously provisioned. You can click the name of a Service Point v4 instance to display additional information.

For more information on provisioning Service Point v4 instances on VMware, cloud environments, or Cisco ENCS devices, refer to the following sections:

Warning: Service Point v4 introduces the ability to easily access the Service Point v4 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 Service Point v4 instance.