Redundand DNS Server


hi,

i know solution have redundancy following setup:

 

windows server 1

ad / dhcp / dns / file server

 

windows server 2

redundand server failover server1.

 

server 1 set 192.168.0.1, clients connected using 192.168.0.1 primary dns. 

 

now question is, if server 1 fails, computers run slow , unresponsive primary dns dead.  server 2 needs set additional domain controller, dns?  how set dns redundand in case server 1 fails?  same question dhcp.

 

thanks in advance.

 

hello,

proceed that:

  • promote second server additional dc
  • install dns service on
  • make gc server

after ad replication, dns ad-integrated zones replicated second dc. so, make sure domain zones ad integrated.

after make each dc points primary dns server , other 1 secondary one. also, configure client computers use second dc secondary dns server.

this ensure high-availability of ad/dns service , reduce risk of losing domain.

for dhcp, can use 50/50 dhcp rule (ip addresses assign divided on both dhcp servers. ensure high-availability of dhcp service , permit avoid conflits of ip addresses assigning.

note both dcs used authentication , ldap queries.

 


this posting provided "as is" no warranties or guarantees , , confers no rights.

microsoft student partner 2010 / 2011
microsoft certified professional
microsoft certified systems administrator: security
microsoft certified systems engineer: security
microsoft certified technology specialist: windows server 2008 active directory, configuration
microsoft certified technology specialist: windows server 2008 network infrastructure, configuration
microsoft certified technology specialist: windows server 2008 applications infrastructure, configuration
microsoft certified technology specialist: windows 7, configuring
microsoft certified professional: enterprise administrator



Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607