Creating a site - BlueCat Edge - Service Point v4.x.x

• Add identity information to queries: DNS queries include a mapping of user IDs, in addition to client IP addresses. This information is retrieved by the identity service when Azure Event Hub is configured to use Microsoft Active Directory. This authorization allows requests to extract data from the event logs stored in Azure Event Hub.
  Note: You must have identity services enabled to collect this information. For more information, refer to Identity services.
• Randomize host record order in Answer section: DNS Resolver Service shuffles responses in the Answer section that match the QTYPE of the query. The shuffled responses are limited to A, AAAA, MX, NS, PTR, and SRV QTYPEs.
• Custom SOA for Edge-policied responses: Updates the SOA definition for DNS queries that are modified based on a BlueCat Edge policy, such as blocking a query or removing unhealthy answers. When enabled, enter the following information:
  • Authority zone: The FQDN of the DNS zone for which the SOA record is authoritative.
  • Primary name server (MNAME): The FQDN of the primary name server for the zone.
  • Zone admin email (RNAME): The email address of the domain administrator, represented as a domain name. For example, admin.example.com
  • Minimum TTL: (Optional) The minimum TTL value of the zone, in seconds. The value must be between 0 and 86400 seconds inclusively. If left blank, the default value is 300 seconds.

• Edge cloud console: DNS queries are stored in your Edge Cloud Console.
  Note: If the Edge Cloud Console option is not selected, DNS queries will neither be stored nor visible in your Edge Cloud Console.

  For more information on custom logging, refer to Custom Logging.

• Custom logging endpoint: DNS queries are sent to a custom logging endpoint. If you enable this query logging option, select a logging endpoint in the dropdown.
  Note: You must create at least one logging endpoint to select the Custom logging endpoint option.

Starting in DRS v3.7.0, when a query comes in for a namespace where all the configured forwarders are unreachable, it temporarily marks all forwarders as down and skips them for any queries in that namespace until they become available. Health checks are performed on the forwarders every second and after 5 failed attempts to resolve a query, it marks the forwarder as down until a single successful response is received. This accelerates the DNS response time to the client and logs the timed-out queries as a SERVFAIL.

If SERVFAIL is added as a condition to the Response Code, DRS will try to resolve the query in the next available namespace configured on the site.

• Health check configurations: enter the name of the health check configurations that the site will use to verify the health of the endpoints.

  For more information on custom logging, refer to Configuring GSLB rules.

• GSLB rules: enter the name of the GSLB rules that will be used to evaluate incoming queries from the site.

  For more information on custom logging, refer to Configuring GSLB health check configurations.

• Under Additional GSLB settings, select the following additional GSLB option:
  • Set TTL for DNS response: select this check box to set a maximum TTL for DNS responses sent to clients for queries that match a GSLB rule.

    If you select this check box, enter a custom TTL value in the DNS record TTL field, in seconds. The value must be between 0 and 604800 seconds inclusively. The default value is 5 seconds.