Basic functional testing
Once an architecture has been defined and a configuration has been implemented it is important to fully test the Edge deployment to simulate all expected client activities. This can be done easily by sending test queries to a provisioned Service Point running a DRS instance and inspecting the results in the Edge management console to see exactly what was done to resolve the query, what policies may have been triggered, and what answer was returned to the client. It is useful to send the same DNS queries to the existing DNS infrastructure (bypassing Edge) so that a comparison can be made between the responses to highlight any potential issues (or benefits) resulting from the configuration.
Testing DNS activity
In BlueCat Edge, select the DNS activity view.
You should see your DNS queries from the testing that was performed. Use this information to validate that the queries were handled in the expected manner and the responses are appropriate for the given test client.
Expand the test
Modify the DHCP setting for DNS Servers in the test network(s) to the Service Point's IP address. If you are using BlueCat DNS Integrity, override the setting previously found under Deployment Options, then deploy the change to your DHCP server.
DHCP clients in the network will now automatically use the Service Point for DNS service. For new DHCP clients, this will take effect immediately. Existing DHCP clients will begin to use the Service Point for DNS when their DHCP lease renews, or you can invoke a DHCP renewal on the client to make the change take effect immediately.
Static (non-DHCP) clients in the network can be manually configured to use the Service Point for DNS. For a Windows client with static network configuration (for example), specify the IP address of the Service Point in the Preferred DNS server field in the IPv4 Properties of the Network Connection.