Need a Windows 2000 Server converted to Forward outside DNS requests.

I'm running Win2000 network with several member servers and 1 DC running DNS (inside rounter/firewall).  I'm adding a 2nd DC which will run DNS and provide backup support in case the 1st DC crashes.  Recently ran DCPROMO and converted W2K Pro and XP Pro hard drives to NTFS. I configured TCP/IP DNS settings to point to my ISPs DNS server as primary and my root DNS server as secondary (added a second DNS server for ISP also).  I know the workstation PCs DNS settings need to point to my two inside DNS servers for Active Directory to function efficiently, so I believe I will need to add a DNS forwarder server for outside Internet traffic.  Does this DNS forwarder server have to be a W2K or 2003 Domain Controller running DNS ?  Or, is there a better way to route Internet traffic from my local network without my servers being online?  
Who is Participating?
Debsyl99Connect With a Mentor Commented:


Ok normally - you never put ISP dns namesrvers in preferred dns server in tcp/ip. You only ever put it in forwarders. Your dns zones should be active directory integrated - and able to accept dynamic updates. In win 2k you need to delete the root "." zone to add a forwarder - in windows 2003 server you can add the forwarder anyway I believe (just getting to grips with 2k3). I'd add your ISP nameserver IP ONLY as a forwarder - maybe configure dc1 to point only to itself - dc2 to point to dc1 and itself as preferred and alternative dns. Clients can then point to both dc's - main dns as preferred dns - secondary as alternative. I also you believe that you could use forwarders on both servers actually,

Deb :))
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.