<div>
<div class="content wysiwyg-content">
I have a quick question that relates to my own conceptual understanding.<br />
<br />
I have a domain controller that is setup as our LANs DNS server using active directory integrated DNS. &nbsp;This server is using Root Hints and not Forwarders for our networks public DNS resolution.<br />
<br />
I am just wondering, are Root Hints completely independent for DNS resolution, in the sense that the Domain Controllers will be pulling down DNS info from these preconfigured root DNS servers? &nbsp;Or does there still need to be additional DNS settings somewhere, like on your router pointing to your ISP or OpenDNS or Google or something? &nbsp;I know this is exactly what forwarders do. &nbsp;So the answer I am expecting is no, and that root hints will allow for DNS resolution all by them selves. &nbsp;Also, the two Domain controllers network card settings are pointing to each-other as primary and themselves as secondary to stop the DNS island effect.<br />
<br />
I just want to make sure, that when we move offices and our WAN ISP information changes that our domain controllers will still be able to do DNS resolution as long as our router has its new WAN IP, default gateway, and subnet mask, while of course the internal IP scope remains the same.<br />
<br />
thanks
</div>
</div>


I have a quick question that relates to my own conceptual understanding.

I have a domain controller that is setup as our LANs DNS server using active directory integrated DNS.  This server is using Root Hints and not Forwarders for our networks public DNS resolution.

I am just wondering, are Root Hints completely independent for DNS resolution, in the sense that the Domain Controllers will be pulling down DNS info from these preconfigured root DNS servers?  Or does there still need to be additional DNS settings somewhere, like on your router pointing to your ISP or OpenDNS or Google or something?  I know this is exactly what forwarders do.  So the answer I am expecting is no, and that root hints will allow for DNS resolution all by them selves.  Also, the two Domain controllers network card settings are pointing to each-other as primary and themselves as secondary to stop the DNS island effect.

I just want to make sure, that when we move offices and our WAN ISP information changes that our domain controllers will still be able to do DNS resolution as long as our router has its new WAN IP, default gateway, and subnet mask, while of course the internal IP scope remains the same.

thanks

How Do DNS Root Hints on a DC integrated DNS server work?

The Internet Protocol (IP) is the principal communications protocol in the Internet protocol suite for relaying datagrams across network boundaries, organized in abstraction layers, traditionally called "Link," "Internet," "Transport" and "Application”. Its routing function enables internetworking, and essentially establishes the Internet. IP defines packet structures that encapsulate the data to be delivered. It also defines addressing methods that are used to label the datagram with source and destination information.

Internet Protocols

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).