Where this offering fits
BlueCat Edge concerns intelligent DNS forwarding at a defined network boundary. The design should explain query paths, upstream dependencies and intended policy rather than treating forwarding as a transparent detail. Resolution behaviour can affect both security visibility and application availability.
Architecture and rollout decisions
Map branches, forwarding rules and existing resolvers. Confirm supported deployment and policy requirements for the selected configuration. Test representative internal and public names, exceptions and upstream failure. Record which team owns changes and how a wrong forwarding decision is detected and reversed.
An evaluation scenario for this offering
Prepare a query set containing an internal application name, a public service and a name with an approved forwarding exception. Record the expected upstream and answer for each. Send the queries through the proposed Edge arrangement and compare observed handling with that intent. Then make one test upstream unavailable and inspect the supported recovery and notification behaviour. Have a second administrator trace an incorrect result using the handover information. The evaluation should produce a comprehensible forwarding policy and a workable correction path, not merely confirm that a single public website resolves after the network change.
Evidence to request for this scope
- Document query-routing intent and upstream ownership.
- Validate split-resolution and exception cases.
- Test the approved failure and rollback path.