superaz300 Posted September 17, 2013 Posted September 17, 2013 Hello Guys, I don't know if anyone can help me, but we have 2 DC's here which the First is Windows Server 2008 R2, and the second domain controller is Windows Server 2003 R2. Both have DNS installed however some sites take ages to resolve. I have no idea what to set the Root Hints or forwarders to, can you guys give me some idea? Also, on the first Domain Controller, IP Configuration: IP Address: 192.168.0.16 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.0.1 Preferred DNS Server: 192.168.0.17 Alternate DNS Server: 127.0.0.1 On the second Domain Controller, IP Configuration: IP Address: 192.168.0.17 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.0.1 Preferred DNS Server: 192.168.0.16 Alternate DNS Server: 127.0.0.1 Is this configuration ok? Its just some sites, for example Facebook, it takes ages to resolve I dont know why. Thanks Guys, James
john Posted September 17, 2013 Posted September 17, 2013 In DNS the Forwarders should be your ISP's DNS Servers (or Google / Open DNS as appropriate). General Client PCs should have DNS of the Internal DNS Servers mentioned above but not the external ones.
superaz300 Posted September 17, 2013 Author Posted September 17, 2013 Hello John, Thanks for your reply, Should I set the forwarders on both servers or just the forest root domain controller? Also, do I need to delete the root hints, I am new to this but I was think of using google DNS, which is 8.8.8.8 and 8.8.4.4, do I just set them as the forwarders and then things should resolve? James
john Posted September 17, 2013 Posted September 17, 2013 On both DNS Servers set the forwarders as your chosen external DNS Servers (so you have said Google's) and that way when your clients (ensure DHCP is giving both IPs for your two DNS Servers out to clients) then they will both work fine. Leave the roothints alone they will be fine as they are so no need to touch them. Yes once they are set external stuff should resolve fine in theory DNS console has to quick tests in it as well you can do on Internal and External. 1
superaz300 Posted September 17, 2013 Author Posted September 17, 2013 Thank John, I applied that, restarted all DNS and DHCP and now sites are resolving fine. Thank you so kind, James
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now