Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 592
  • Last Modified:

SBS2003 DNS problems - client pc internet is intermittently slow

I have an SBS2003 server with 10 client pcs.

Just recently I have added a 4 new forward lookup zones in the DNS configuration. This seems to have caused the client pcs internet connection to slow quite dramatically; either internet requests timeout or the pages (such as yahoo or google) take up to 30 seconds to load. However there are times when the internet is running well which I presume is due to caching either on the server or the clients.

The server has the following services running: iis, dns, exchange & sql but does not have IAS. I plugged the internet connection directly into a laptop and it works very well.

Does anybody have any suggestions for solving this problem?
I have searched the internet without much luck. Is there a way to boost the DNS priority on the server to improve it's response time?
0
andychilds
Asked:
andychilds
  • 4
  • 3
1 Solution
 
andychildsAuthor Commented:
I have been troubleshooting the problem this morning and on the first try to sites (such as google.com, yahoo.com) an nslookup will time out 2-3 times before finally finding the correct ip address.
0
 
oBdACommented:
Have you configured your machines to use an outside DNS server in the TCP/IP settings? If so, change that to use *only* your SBS as DNS server, and configure forwarders to point to your ISP's DNS server.

10 DNS Errors That Will Kill Your Network
http://mcpmag.com/features/article.asp?EditorialsID=413

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/?kbid=825036
0
 
andychildsAuthor Commented:
The client PCs are configured to look at the server and I have configured two dns forwarders.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
Chris DentPowerShell DeveloperCommented:

The first thing I would suspect is the Forwarders. Remove those and see if you still get slow resolution.

Without them your server will use the Root Hints file (the servers listed under the Root Hints tab in the Properties for your DNS server), then it works down from those servers to get to the right domain - and you really shouldn't notice a speed issue with that.

Chris
0
 
andychildsAuthor Commented:
Thanks Chris-Dent, that has improved the performance.

But why has this made a difference though? I have been using dns forwarder ip addresses for over a year; why would it suddenly change?
I can only think that it is caused by the forward lookup zones I have added for the domain names that I host on the server. I have been adding them as primary zones, and then adding 'a name' records for www; is this the correct?
0
 
Chris DentPowerShell DeveloperCommented:

> But why has this made a difference though? I have been using dns forwarder ip addresses for over a year;
> why would it suddenly change?

I couldn't say really... you're effectively handing off all the work to an upstream DNS, in this case your ISPs DNS. You would have to ask them to try and fix the problem - if they even admit there is one or can find it.

It could be something as simple as the server they use is getting old and generally getting unresponsive. Or they've got a lot more traffic being handled by it now.

Anyway, the change you've made means that instead of relying on your ISPs DNS to do all the running around your own server will do it. I normally prefer that configuration anyway simply because you don't have to put up with whatever happens at your ISP.

> I can only think that it is caused by the forward lookup zones I have added for the domain names that I
> host on the server. I have been adding them as primary zones, and then adding 'a name' records
> for www; is this the correct?

It should have no effect on name resolution except within the domains you have explicity added - and that's entirely intentional. There's certainly no reason for it to effect it in a more general sense.

Chris
0
 
andychildsAuthor Commented:
Thanks very much Chris for all your help.
0
 
Chris DentPowerShell DeveloperCommented:

It's a pleasure.

Chris
0
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.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now