Windows 2003 SBS DNS problem

I have a small business network setup with 1 server acting as the DC, DNS server, and DHCP server utilizing AD. I have 5 other computers that all have win xp pro on them. It takes over 2 minutes for the xp clients to login. I am almost positive that I have a DNS issue but can not figure out how to get everything working properly.
The present configuration =    internet ------->Fractional T1 modem -------->Netgear Router w/8 port switch ----->then I have all the clients and the server connected to the netgear router/switch.
The router has a static IP and I do not have it set to be a dhcp server because the win 2003 SBS server is the dhcp server. When I do nslookup I it returns the name of the sever but the logins are still slow. I also have the gateway for the server and the clients set to the internal netgear router ip  
(ex.  Do I need to have the clients gateway set to the win 2003 SBS server's ip address?  Any help is greatly appreciated!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Your DNS settings are incorrect. The following setup should work for you:

*** TCP/IP-Settings ***
* On your DC/DNS, make sure the only DNS listed in the TCP/IP properties is itself.
* On your domain members, enter only the DCs as primary DNS.
* Do NOT enter your ISP's DNS server in the TCP/IP settings on any domain member. All DNS resolution needs to be done by your internal DNS server *only*.

*** DNS Server Settings ***
* Delete the root zone (if present) in your DNS server's forward lookup zones (the single dot, "."), to enable external lookups.
* Right-click your forward and reverse lookup zones, go to Properties, and make sure that Dynamic Updates are enabled.
* In the properties page of your DNS servers, configure forwarders to point to your ISP's DNS. The forwarders section is the *only* entry in your network where your ISP's DNS should be listed.
* It's recommended (but not necessary) to set your zones to Active Directory integrated (this can be done in the properties of the zones as well).

Once you've checked this, open a command prompt and enter "ipconfig /registerdns", then stop and re-start the netlogon service. Check if the SRV records have been created (see link below).

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003

How to Verify the Creation of SRV Records for a Domain Controller

How Domain Controllers Are Located in Windows

How Domain Controllers Are Located in Windows XP

SRV Resource Records May Not Be Created on Domain Controller

HOW TO: Configure DNS for Internet Access in Windows Server 2003

HOW TO: Troubleshoot DNS Name Resolution on the Internet in Windows Server 2003

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
one thing you mentioned concerns me,, when you said:

When I do nslookup I it returns the name of the sever but the logins are still slow

that would be a reverse dns lookup (resoving IP to name)

what happens when you do a regular dns lookup (Name to IP)?? does it resolve to the IP address of the DC?
ie  nslookup

can you ping the DC by IP address and by domain name?
jgroh9Author Commented:
one quick question...what do I do with the dns server addresses that are used for my isp which are currently configured in my router? Do I leave them there? I believe that I have to?
Your ISP's DNS servers go into your DNS server's forwarders entries. Your DC/DNS will then answer your internal queries, and when it encounters a query for a domain it isn't responsible for, it will forward the request to your ISP's DNS server.
jgroh9Author Commented:
Thanks for your help oBda. I checked all the settings you suggested and I had most of them setup correctly. The problem was that I didn't name the server correctly. When I named the server I named it server01.domain but instead it should have been server01.domain.local
A silly mistake but in the end I learned a lot from it.
Thanks again for all your help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

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.