Symptoms
Bot profile requires a DNS resolver to fully operate. The DNS resolver needs to be under the default Route-Domain. A warning message displays when there is no DNS resolver, but it does not state that the DNS resolver should be configured for the default Route-Domain.
Impact
Warning message is inaccurate: a DNS resolver is configured (under a different route domain), but the feature does not fully operate.
Conditions
-- Bot defense profile (with signature enforcement) is in use.
-- DNS resolver is configured under a non-default Route-Domain.
Workaround
Configure the DNS resolver under the default Route-Domain.
Fix Information
This release contains a warning message that indicates that the DNS resolver should be configured under the default Route-Domain.
