Assigning DC members the correct DNS addresses

[MockY]

Here is the scenario:

I have a 40+ client network. They authenticate through my Win2k3 server. Everything works just great except one thing. The clients are assigned the server's ip number as their dns, whicg is totally fine (otherwise it would take a while to log them in). However, I want their primary DNS to be the DNS my ISP is using. As of now, I manually enter it on every client in order for them to surf the internet, but the DHCP only assigns the servers IP, this the clients can't surf.

So what should I do?

 

[Roadki11]

Yicks, thats not how you want to do it. Domain pcs should only ever point to local domain dns server, in your case the domain controller. The only secondary dns server they should have is an alternate local dns server. You need to setup dns forwarders in your local dns server, see the following link:

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

RoadKi11

 

[WhoKilledKenny]

If you ISP doesn't require authetication to get out on the Internet via PPPoE, your local DNS server should use Root Hints.
By default, a Microsoft DNS server connects to the Internet to process DNS requests more with root hints. When you use the Dcpromo tool to promote a server to a domain controller, the domain controller requires DNS. If you install DNS during the promotion process, a root zone is created. This root zone indicates to your DNS server that it is a root Internet server. Therefore, your DNS server does not use forwarders or root hints in the name-resolution process.

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

If you can aviod using your ISPs DNS, I would as if it were to go offline, you could be stuck.

 

[jshurst]

I agree with Roadki11. You want your local clients to connect quickly to your own DC and then forward requests. Set up the forwarders (not forward lookup zones). I've been using

http://www.opendns.org

's dns servers in my forwarders tab and so far so good. They seem to be good and fast.