RE: DNS problems

["Ian" <ian@xxxxxxxxxxxxxxxxxxxxxxxx>]

If your Server 2003 is using AD then the domain controller *must* perform
the DNS server role on your network. (in a simple environment)

http://support.microsoft.com/kb/291382

You are probably seeing a whole bunch of other things going wrong too -
slow
logins, browsing, cripplingly slow access to shares, sluggishness on
accessing internet sites etc.

>From the technote:

Question: Should I point the other Windows 2000-based and Windows Server
2003-based computers on my LAN to my ISP's DNS servers?

Answer: No. If a Windows 2000-based or Windows Server 2003-based server or
workstation does not find the domain controller in DNS, you may experience
issues joining the domain or logging on to the domain. A Windows 2000-based
or Windows Server 2003-based computer's preferred DNS setting should point
to the Windows 2000 or Windows Server 2003 domain controller running DNS.
If
you are using DHCP, make sure that you view scope option #15 for the
correct
DNS server settings for your LAN.

Question: Do I need to point computers that are running Windows NT 4.0 or
Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows 98 Second
Edition to the Windows 2000 or Windows Server 2003 DNS server?

Answer: Legacy operating systems continue to use NetBIOS for name
resolution
to find a domain controller; however it is recommended that you point all
computers to the Windows 2000 or Windows Server 2003 DNS server for name
resolution.

Question: What if my Windows 2000 or Windows Server 2003 DNS server is
behind a proxy server or firewall?

Answer: If you are able to query the ISP's DNS servers from behind the
proxy
server or firewall, Windows 2000 and Windows Server 2003 DNS server is able
to query the root hint servers. UDP and TCP Port 53 should be open on the
proxy server or firewall.