DNS recommendations from Microsoft
March 8th, 2011 by Awinish Vishwakarma and tagged DNS/DHCP
Many forum/post, often i see a question, how to configure DNS in my domain controller, is primary point to itself or secondary DNS server, is it OK to configure loopback IP & what are the best practices etc.
I would not cover everything, leave for the below link to answer for you. Few things, i would like to mention
- NEVER use public IP configured directly in the NIC either of the DC or clients.
- Public IP(ISP DNS) used for external domain name resolution,should always be configured in Forwarder of DNS servers.
NedPyle from Microsoft has got recommended & best practices for DNS. So next time you aare confused or looking for best practices follow the below link.
http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail-sack-saturday-edition.aspx
Posted in Directory Services, DNS/DHCP, Exchange | 4 Comments »
March 26th, 2012 at 11:54 pm
Dear Mr.Awinish,
Could you please tell me, How can i make an additional domain controller as failover in windows 2008 Standard 64 bit??? If Primary is down , i need to switch automatically to secondary (Additional Domain)?? is there any Option to do that??
2. I need to WAN to UP if Primary Domain is failure?? Any Option to do that??
Thanks for your kind attention and looking forward your prompt reply in this regard.
March 27th, 2012 at 9:39 am
There is no such option available with AD and actually you don’t require it even. If the DC holding FSMO goes down there is no immediate impact. Its simple you can seize FSMO role on the other available DC and perform metadata cleanup for the failed DC and reconfigure it back and its pretty simple.
March 26th, 2012 at 11:54 pm
Dear Mr.Awinish,
Could you please tell me, How can i make an additional domain controller as failover in windows 2008 Standard 64 bit??? If Primary is down , i need to switch automatically to secondary (Additional Domain)?? is there any Option to do that??
2. I need to WAN to UP if Primary Domain is failure?? Any Option to do that??
Thanks for your kind attention and looking forward your prompt reply in this regard.
March 27th, 2012 at 9:39 am
There is no such option available with AD and actually you don’t require it even. If the DC holding FSMO goes down there is no immediate impact. Its simple you can seize FSMO role on the other available DC and perform metadata cleanup for the failed DC and reconfigure it back and its pretty simple.