DNS and 2008 R2 Server

[swinnie]

Hi Guys,

At work we've got a 2008 R2 server, which is running an HP Server in an ESXi Virtual Machine. It controls the domain, DNS, DHCP and Exchange server. We've also got the terminal server virtualised on the same server.

However, I'm not too sure on it's DNS configuration as I was looking at the settings that were configured by my colleagues.

Obviously the server needs a static IP Address, but should the DNS point to the server itself?

How should the server resolve anything 'external to the network'. I've seen 'forwarder' style settings, but want to understand them a bit first.

Any related reading would be appreciated.

Many Thanks

 

[PAz]

yes its fine pointing to itself (I assume its your only DNS server right?)

it can forward to your isp [/or use root hints to resolve external addresses]
right click the server name in the dns console and go to properties to see what its using

http://technet.microsoft.com/en-us/network/bb629410

heres a nice explaination of forwarders: http://technet.microsoft.com/en-us/library/cc782142(WS.10).aspx

 

[ecksmen]

Hi Guys,

At work we've got a 2008 R2 server, which is running an HP Server in an ESXi Virtual Machine. It controls the domain, DNS, DHCP and Exchange server. We've also got the terminal server virtualised on the same server.

However, I'm not too sure on it's DNS configuration as I was looking at the settings that were configured by my colleagues.

Obviously the server needs a static IP Address, but should the DNS point to the server itself?

How should the server resolve anything 'external to the network'. I've seen 'forwarder' style settings, but want to understand them a bit first.

Any related reading would be appreciated.

Many Thanks

Server 2008R2 has some nice validation tools built into the server manager console. It'll check things like the AD records etc... It'll tell you you should have the servers IP as the primary DNS, a secondary DNS but that you should also have the loop back address in the list but not as the primary.

Some people will suggest root hints is the correct way of configuring DNS but it really depends upon your network and users. On a busy network root hints is my favour approach as the local DNS cache of the DNS server will soon fill up. However on low traffic DNS servers forwarders to a say an ISP dns is considered faster as you're not trawling the internet for root servers.

http://www.grc.com/dns/benchmark.htm < bnsbench is a good tool, or atleast will give you an idea. Just don't forget to clear the DNS servers cache, as well as the local network cache when benching root vs forwarders.