DNS Edge operational best practices - BlueCat DNS Edge

DNS Edge Deployment Guide (Fleet Service Point)

Locale
English (United States)
Product name
BlueCat DNS Edge

DNS Edge service point and Fleet Service Point monitoring and troubleshooting

During the course of operation, there is little need to monitor the service points and Fleet Service Points. Service points and Fleet Service Points respond to PING, polled for access to UDP/TCP port 53, and also have a helpful URL which can be used to monitor their status:

  • http://{SP IP address}:80/v1/status/spDiagnostics Review more detailed information about a DNS Edge service point.
  • http://{Fleet Service Point IP address}:80/v2/diagnostics Review more detailed information about a DNS Edge Fleet Service Point.

The BlueCat service operations cloud has visibility into all micro-services for the service points, Fleet Service Points, and DNS Edge Clouds, and all activity is logged for troubleshooting purposes. System monitoring is being completed by cloud native tools managed by the BlueCat cloud operations team.

Incident response considerations

DNS Edge provides great visibility into client DNS traffic, incorporating DNS Edge policy application into your existing incident response process. DNS Edge makes it easy to respond to security events such as anomalous traffic, or suspicious or malicious behavior detected by DNS Edge. DNS Edge can immediately allowlist or blocklist websites or individual clients. Individual clients can be redirected to a remediation site or a warning site.

BEST PRACTICE: Define an operational process to address security concerns identified by DNS Edge.