<div>
<a href="http://technet.microsoft.com/en-us/library/cc732584.aspx" rel="ugc">http://technet.microsoft.com/en-us/library/cc732584.aspx</a><br />
<br />
hope this helps!
</div>


<div>
Install your dns with AD integraded mode.<br />
<br />
For servers outside your domain, configure a dns forwarder and specify your ISP DNS or even google dns 8.8.8.8.<br />
<br />
You may also want to have your dns server to do your dhcp so that it has all the entries even if the clients do not update your dns server.
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
Wondering if anyone can comment on how I would need to implement this:<br />
<br />
We have a small network of with and AD server and some PC I would like to implement DNS on the domain controller to make it easier for clients to find services. &nbsp;Ideally to keep it simple I would define some static Name to IP address mapping and then point anything that is not local to ISP.<br />
<br />
Is this possible and what briefly would I need to configure in server 2008 R2 to get this running, domain controller is also doing DHCP.<br />
<br />
Thanks in advance
</div>
</div>


Hi,

Wondering if anyone can comment on how I would need to implement this:

We have a small network of with and AD server and some PC I would like to implement DNS on the domain controller to make it easier for clients to find services.  Ideally to keep it simple I would define some static Name to IP address mapping and then point anything that is not local to ISP.

Is this possible and what briefly would I need to configure in server 2008 R2 to get this running, domain controller is also doing DHCP.

Thanks in advance

http://technet.microsoft.com/en-us/library/cc732584.aspx

hope this helps!

Install your dns with AD integraded mode.

For servers outside your domain, configure a dns forwarder and specify your ISP DNS or even google dns 8.8.8.8.

You may also want to have your dns server to do your dhcp so that it has all the entries even if the clients do not update your dns server.

Server 2008 Local DNS

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.

Windows Networking

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.