• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 372
  • Last Modified:

OpenDNS over riding our Internal DNS ....

We are having an issue with OpenDNS over riding our Internal DNS when we put OpenDNS servers as our backup DNS servers in the DHCP scope for our internal network.  As of this time, we have (2) Internal DNS servers and we added (2) OpenDNS servers in our DHCP scope options.  However, we are finding that more and more clients are complaining because when they try to access our internal network, it is OpenDNS responding instead of our Internal DNS servers which result in a temporary loss to our internal resources.  Has anyone else experienced this?  Is there a fix for this?  What is actually happening to cause this?  Any help or suggestions would be greatly appreciated.  ///  Candice
1 Solution
Chris DentPowerShell DeveloperCommented:

Hi Candice,

Clients on an AD Domain should only have DNS servers listed that can answer for the AD Domain.

If you wish to use the OpenDNS servers, configure them as Forwarders on your Internal DNS servers. Don't give them to clients directly because you won't be able to stop them sending queries there on occasion.


Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now