what is the best way to setup DNS on a windows 2003 server that is your Domain controller?

Had DNS running on two servers. Both domain controllers. One was my SQL 2005 server(was told to remove DNS and Domain Controller roll because of upgrade to SQL and or Accounting software (Dynamics Great Plains 10.0) and the other was running Print server, DHCP Server and file server (this one is my oldest server Pentium 3). I have a seperate Exchange 2003 & SQL Servers. I recently baught a new dual quad core zeon server with raid 5. I added DHCP and DNS to my new server and removed DNS from the SQL Server, and then removed DHCP from my old file server. It all seems to work, but the network (on a gigabyte back bone with 2 by 6 MB cable internet) seems to run extremely slow. I am also using a Harware firewall/VPN device made by WatchGuard).  
Who is Participating?
NetAdmin2436Connect With a Mentor Commented:
Yes, Your domain controller should run DNS and point to itself for DNS. Then on your domain controller in DNS management you can have your IPS's DNS as a forwarder only. In DHCP, make sure all your clients are pointing to your internal DNS server (domain controller) ONLY. Do not point your clients to your ISP's DNS!
NetAdmin2436Connect With a Mentor Commented:
Some of your clients may still be pointing at your old DNS server. As long as your DHCP is setup correctly and have DNS pointing to ONLY your current DNS server (domain controller).

On all client computers you can
Start --> run --> ipconfig/release
Opps, forgot cmd...

Start --> run --> cmd --> ipconfig/release
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.