Win2003SBE/Domains/DNS Setup

[killerpcs]

I am looking for some ideas on the best DNS setup for the following:
Network consists of a Win 2003 SBE server, and 5 Win XP Pro PC's.
Internet connection is DSL through an ISP.
With the PC's setup on the servers domain, login to the domain is extremely slow, I found that the PCs had the DSL ISP's DNS server IPs, so I think they may have been going out to the internet looking for the local domain. I changed the setup on the PC's, so that they are looking at the 2003 server for DNS, and the server is set to forward requests it cant resolve to the ISP's DNS servers. With this setup, the login is quick on the PC's, and all are able to get out on the internet.
I guess my question is, what is the ideal setup, or is there such a thing for this configuration?
thanks,
Dave

 

[GeekDrew]

The current setup is correct.

Client --> Local Server --> Remote Server --> Up the heirarchy (Internet?)

 

[PawNtheSandman]

You did everything right.

 

[ktwebb]

If you only have one local DNS server, what I have done typically anyway, is set the local AD DNS server as the primary DNS server and one of the ISP's DNS server as the secondary DNS server. That way, if your LOCAL DNS server is down, the clients can still at least get out to the internet. Just a redundancy thing. Local DNS should be done first so authenticating is timely.

 

[killerpcs]

Thanks KT, I will give that a shot, as part of the problem is that they are always experiencing power issues, that bring down their DSL, and once its back and functioning they always have issues with the internet connection, I havent figured out yet why the server wouldnt recover itself from a lost connection.