About DNS, DHCP, and Windows Server 2008 Virtual Labs

How Domain Controllers Are Located in Windows

Installing Network Monitor

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Add/Remove Programs.
3. Click Add/Remove Windows Components.
4. Click Management and Monitoring Tools, and then click Details.
5. Click to select the Network Monitor Tools check box, and then click OK.
6. Click Next.

148942  (http://support.microsoft.com/kb/148942/EN-US/ ) How to Capture Network Traffic with Network Monitor

124837  (http://support.microsoft.com/kb/124837/EN-US/ ) Connecting to a Remote Network Monitor Agent Across a Router

Generally speaking, DNS and DHCP are separate infrastructure networking services which provide name resolution and IP address lease. There are several inter-function that I can remember:

 

1. DHCP distribute the options such as DNS server address (006) and domain suffix (015) for name resolution on the clients.

 

DNS server address (006):

 

The DNS server address in the domain for internal name resolution or external name resolution.

 

 

domain suffix (015):

 

The suffix which will be append when you try to resolve single label name in the domain.

 

 

2. DHCP will dynamically register the DNS PTR record for DHCP clients running Windows 2000, Windows XP , or a Windows Server 2003 operating system.

 

Using DNS servers with DHCP

http://technet.microsoft.com/en-us/library/cc787034(WS.10).aspx

I have DHCP and DNS services installed on a Windows Server 2003 (sorry couldn’t find a WS2003 forum).
Under reservations (DHCP) i have no IP addresses or machines listed yet i know a PC that does have static IP (by the PC showing a fountain pen symbol under address lease) – is this correct?
Also i noticed that our server occassionaly has a different IP address to the one we allocated it. (ping from PC it gives a different IP) looking at the properties of the local connection i notice that we have it set to static, but to get the PC to see the correct address i typed /flushdns /registerdns. I have 100 PCs so is it correct to run this command on the server so it can update all PCs DNS to the correct IP of the server?

Ans:

There should only be one IP address registered in DNS for each machine, and that should be its local NIC address. If the remote access address (ie the internal interface if you are using RRAS) registers in DNS, it can cause you all sorts of odd problems.  See KB292822. 
The important thing you should remember is that, never give 192.168.x.x address for RRAS type access. Try to give a different range of address and solve the problem.

DNS

Windows 2003 DNS Best Practices

Basic DNS Concepts

Concepts about DNS

FAQ about Windows Server 2000 and Windows Server 2003

Troubleshooting DNS

TechNet Virtual Labs: Windows Server 2008 R2

http://pragimtech.com/HR.aspx