The thing is I wanted to test it first before I killed my entire 450 pc and 32 lans by messing with AD DNS?? Right now my dns is set to forward all requests to root servers, no caching and no zones other than that board.imcu.com zone we set up last week. Otherwise my forward lookup and reverse lookup zones only have dynamic updates from internal IP's... So if I set my three DC's to forward to OpenDNS the users would get all their internal DNS lan traffic fine and all real Internet traffic would resolve DNS through OpenDNS?? If I understand everybody ok. The link OpenDNS setup send me too was a link to MS stating to delete the [.] zone but I don't see one of those on my DC's???
From: Andrew S. Baker Sent: Friday, November 20, 2009 3:22 PM To: NT System Admin Issues Subject: Re: OpenDNS All you need to do to use it successfully is to setup your current DNS server for Active Directory, to forward to OpenDNS for all remote zones. Then, your clients will get all internal addresses as they do now, and will go to OpenDNS rather than your ISP or looking up the addresses via the Root servers for everything else. Works like a charm. Been using it at home, work and at our church for over a year at this point now. ASB (My XeeSM Profile) Providing Competitive Advantage through Effective IT Leadership On Fri, Nov 20, 2009 at 2:33 PM, David W. McSpadden <dav...@imcu.com> wrote: I am trying it out. I have several web services internally, will they work when OpenDNS is my forwarder? I have a local Intranet as well and it is not working with OpenDNS?? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
