Configuring a DNS Edge Service Point v3 instance - BlueCat Integrity - 9.4.0

Configure an Edge service point on a supported DNS/DHCP Server to allow the service point to process the IPv4 DNS client traffic.

1. Select the Servers tab. Tabs remember the page you last worked on, so select the tab again to ensure you're on the Configuration information page.
2. Under Servers, click a server name.
3. Click the server name menu and select Service Configuration.
4. From the Service Type drop-down menu, select Edge service point.
5. Under Warning: Before Enabling Edge service point Service, click the I confirm that Edge Service Point Service requirements are met. link to review the prerequisites and requirements for configuring the service.
6. Select the check box to confirm that you've reviewed the requirements.
   Note: You must select this check box to proceed with the configuration.
7. Under General Settings, select the Enable Edge Service Point check box.
8. Complete the following fields:
   • CUSTOMER INSTANCE URL: The DNS Edge URL.
   • SITE ID: The DNS Edge site ID.
   • SERVICE POINT IPv4 ADDRESS: The additional IPv4 address previously configured. The service point will listen to this IPv4 address for incoming DNS client traffic.
     Note: If your network infrastructure requires the outbound communication with Edge cloud to go through a HTTP proxy, you can configure the service point to route all outbound HTTPS requests through a HTTP proxy by entering the proxy details in the HTTP PROXY HOST, HTTP PROXY PORT, HTTP PROXY USERNAME, and HTTP PROXY PASSWORD fields.

     • The value you enter in the HTTP PROXY HOST field can either be an IPv4 address or a FQDN.
     • HTTP is the only supported proxy type. SOCKS proxy servers are not supported.
     • Basic authentication with username and password is the only tested and supported authentication.
     • You must configure the proxy server to allow HTTP POST traffic.
     • The proxy server must resolve all DNS Edge Cloud endpoints. For more information, refer to BlueCat DNS Edge system setup in the DNS Edge Deployment Guide.
     • If the service point cannot reach the proxy, it will attempt a direct connection to the target host.
     • The proxy configuration defined when you first configure the service point cannot be edited once the service point is enabled. Any proxy updates will require the service point to be disabled and re-enabled with the necessary changes to the proxy settings.
     • For proxy servers and firewalls with SSL interception:
       • mTLS must exclude or except *.bluec.at from the SSL interception
       • You cannot install certificates as a workaround
9. Under ACCESS KEY SET, select the first radio button, then paste the client ID and secret key from your API access key set in DNS Edge into the Client ID and Secret Key fields.

   Alternatively, select the radio button beside JSON File Upload, then click Choose File to upload the JSON file from DNS Edge that contains the API access key set information. The file name displays next to the Choose File button once you upload it.

   Note: The API access key set must belong to an Edge Administrator or System Administrator. For instructions on generating and downloading the API access key set, refer to Profile in the DNS Edge User Guide.
10. Click Update to save your information and connect to the service point.
    After you click Update, the service point will take approximately 10-15 minutes to register with the Edge cloud and instantiate completely.
    Under Edge Service Point Status, you can check the progress of the initialization. To retrieve the most recent state, refresh your browser. Once the service point registers, the diagnostics become available, which you can review as part of this section.

    Note:

    • Once the service point is successfully registered, you can click the link next to SITE ID to navigate to the corresponding site in the DNS Edge user interface. Under CONNECTED, you will see the service point name. When you click the service point name, BDDS shows under the Host Manager field.

      On the service point details page, the Service IP Addresses field will be populated with all the IPv4 addresses configured on any of the DNS/DHCP server's Service interfaces (eth0, eth1, eth2, eth3) including the IPv4 address the service point was configured to listen on.