mirojr Posted January 8, 2015 Posted January 8, 2015 Hi In regards to an additional domain controllers ipv4 dns settings what is the best way to set this? I am currently set like this: Is it ok? dc01 ip 192.168.1.254 preferred dns 192.168.1.254 dc02 ip 192.168.1.253 preferred dns 192.168.1.254 Thanks
Davit2005 Posted January 8, 2015 Posted January 8, 2015 Have you installed DNS on the additional server, this would be a good thing to look into. Additionally, If you use the same domain controller/s for DHCP look into DHCP load balancing or split the scopes between the servers.
Steve21 Posted January 8, 2015 Posted January 8, 2015 There's a few ways to do it depending on how you want it. But if you're doing it that way I'd use local IP 127 etc rather than actual IP. But we have ours cross point so DC1->DC2->DC3->DC1 etc. Might want to check this out for options and benefits/negatives: http://www.edugeek.net/forums/windows-server-2008-r2/80387-what-should-your-dcs-point-dns.html#post714999 Steve
mikkydoos Posted January 8, 2015 Posted January 8, 2015 (edited) You should be pointing DNS servers to themselves... as primarys anyway Edited January 8, 2015 by mikkydoos
Steve21 Posted January 8, 2015 Posted January 8, 2015 You should be pointing DNS servers to themselves Not according to MS recently it's not. Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain controller and it points only to itself, or points to itself first for name resolution, this can cause a delay during startup. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should be configured only as a secondary or tertiary DNS server on a domain controller. Based on their "best practice analyzer" Steve
mikkydoos Posted January 8, 2015 Posted January 8, 2015 They've changed their tune! Sure have. How many times do you restart your DC's anyway ?
Steve21 Posted January 8, 2015 Posted January 8, 2015 Sure have. How many times do you restart your DC's anyway ? It's not just due to that it causes lots of issues if things get upset, just picked first example The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain controller and it points only to itself for name resolution, it can become an island and fail to replicate with other domain controllers. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller. The loopback address should be configured only as a secondary or tertiary DNS server on a domain controller. etc etc Steve
mikkydoos Posted January 8, 2015 Posted January 8, 2015 (edited) I've just checked mine. 2 DNS's both DC's. Mines is actually set up like @Steve21 DC1 primary = DC2 DC2 primary - DC1 Secondary's point to 127.0.0.1 Must have come across that before Edited January 8, 2015 by mikkydoos
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