Solved

Slow DNS resolution with any new computers

Posted on 2010-09-23
15
694 Views
Last Modified: 2012-05-10
Hello,
      At my company we have one server inside our network that is a primary domain controller  and DNS. Recently i have replaced several employees' computers with new ones. All of the new computers are very slow to load web pages (15 - 20 seconds) even though our internet connection is very fast. Usually running a broadband speed test from any of the computers (even the slow internet ones) results in an absolute minimum of 15Mbps UP/Down (ranges up to as high as 80Mbps). I have discovered that all of the lag in initially displaying a webpage is spent resolving the domain name. If i change the DNS server for those computers from our DNS to automatically detect the internet is instantly fast. Problem is that that screws up all the accessing of shared folders, printers, etc... inside our network.

Any of the computers that have been around since before i was handling IT have fast internet even with the hardcoded DNS server inside our network.

It seems that when i replace a computer i must need to somehow put information about that new computer into the DNS server? I know there must be something simple i am missing, any ideas?

Thank You,
0
Comment
Question by:ruairi
  • 6
  • 5
  • 2
  • +2
15 Comments
 
LVL 6

Expert Comment

by:Dangle79
ID: 33746577
when you set them to automatically detect DNS servers what IPs do they get? these should come from your DHCP
do you have your public (internet) DNS server IPs entered as additional DNS servers?
in my pic the first two are my internal, the bottom two are the public.
Capture.PNG
0
 
LVL 7

Expert Comment

by:JohnThePro
ID: 33746627
Please take the time to read through this TechNet article. It's great, and will help you iron out a lot of DNS related kinks in your network.

http://technet.microsoft.com/en-us/library/cc757837%28WS.10%29.aspx

0
 

Author Comment

by:ruairi
ID: 33746646
if i set my computer to automatically detect DNS server and ipconfig /renew i get 168.95.1.1 as my DNS server, i assume this is public. I have already tried setting up one of the computers with slow internet with our DNS srever (192.168.1.100) as primary, and the above ip address as the secondary. This still results in the very slow internet.
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 33746665

> in my pic the first two are my internal, the bottom two are the public

The bottom two really should not be there if we're talking about AD domains. It causes all manner of problems if the client starts using them (again, while it is part of an AD domain).

Ruairi,

Can you tell us about your DNS server? And can you tell us if that's the only DNS server your clients are configured to use?

I would be especially interested in any Forwarders you have configured. You'll find those by opening the DNS server console, right clicking on the server and opening Properties, then selecting the Forwarders tab.

Chris
0
 

Author Comment

by:ruairi
ID: 33746799
JohnThePro - I have started reading the article, so far no luck but will keep looking. Thanks

Chris - Server Particulars:
Dell Server PE1800
Intel Xeon CPU 3 GHz
4 GB RAM

Windows Server 2003 Standard Edition SP2

It is the only DNS server the clients are configured for.

Forwarders Tab:
DNS Domain List = 'All other DNS domains'
Selected Domain's forwarder IP address list =
208.200.248.1
69.10.201.27
Number of seconds before forward queries time out = 5
Thanks
0
 
LVL 7

Expert Comment

by:JohnThePro
ID: 33746892
Okay, lets baby step through this.

Your workstations, do you statically assign them IP addresses?
If so, did you assign the new workstations the same IPs as the old workstations?
0
 
LVL 70

Accepted Solution

by:
Chris Dent earned 500 total points
ID: 33746913
Thanks. At this stage, and given that you've having trouble, please delete everything from the Forwarders tab.

You might choose to put something back there later, but we need to know if it works better without those than it is with. Your server is quite capable of resolving names without forwarders.

Remember that any clients you have should only use your internal DNS server since AD is involved. You don't want them having an external server as a backup because it just swaps one problem (no fault tolerance) for another (trouble talking to AD).

Chris
0
Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

 
LVL 1

Expert Comment

by:PTSMN
ID: 33747219
maybe try a simple, "ipconfig /flushdns" and "ipconfig /registerdns" from cmd?

0
 

Author Comment

by:ruairi
ID: 33748477
John - No, they are assigned with DHCP. The replacement computers' Computer Names are also different.

Chris - Deleted all IP's from the forwarders tab. The 'All other DNS Domains' entry in the DNS Domains list cannot be deleted.
This change had no effect on the problem workstations (i gave it over an hour before trying in case there would be some time lag).

PTSMN - Sorry if this is a stupid question, but i assume that would be on the workstations, not the DNS server?

Thanks for all your comments so far,
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 33748663

Great, so can we test DNS resolution a bit.

How quickly do you get responses for:

nslookup www.google.com
nslookup experts-exchange.com
nslookup www.microsoft.com

The response should be pretty much instant in all cases, if there's a delay we need to dig further.

Chris
0
 

Author Comment

by:ruairi
ID: 33749388
Thank you all for your input and attempts to help. It turns out Chris-Dent's comment at 11:07am was the answer (just took a while to work), so i will go back and accept that as the solution. I just wanted to take a minute to thank everyone that tried to help.
0
 

Author Closing Comment

by:ruairi
ID: 33749401
Thanks, this has been plauging me for a while and getting rid of the forwarders took care of it. Hopefully it wont cause problems with interoperability with our trusted domain at another site.
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 33751814

I just wanted to add one last comment.

It's quite likely that one or more of the forwarders you had was broken. Replacing those with working forwarders would also solve this problem. If none are easily available you can use Google's public DNS servers:

http://code.google.com/speed/public-dns/

Anyway, leaving it using Root Hints is not a problem :)

Chris
0
 

Author Comment

by:ruairi
ID: 33753284
Thanks for the tip! Do you have any guesses as to why computers that have been in our network for years would not see the slow resolution and new ones would?
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 33753616
Not really, at least not unless they have different DNS servers configured.

DNS (because it's UDP based) doesn't acknowledge connections, so the client has no way of knowing if a DNS server is going to respond except by waiting.

In your case it's quite likely that one (or both) of the forwarders were timing out, which results in a very very slow response to the client machine.

Chris
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

If you have a multi-homed DNS setup in windows, you can have issues with connectivity to the server that hosts the DNS services (or even member servers of your domain if this same DNS server is a DC). This is because windows registers all of its IPs…
I will assume you are running a non-server version of some sort of Windows throughout this article. There are many flavors of Windows since Windows Server 2000 - 2008, XP Home & Pro, Vista Home & Pro, and Windows 7 Starter, Home, Pro, Ultimate, etc.…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

759 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now