Solved

Trace DNS query and lookup time

Posted on 2011-03-01
4
636 Views
Last Modified: 2012-05-11
I am experiencing problems with 1 web site, it appears to be a DNS problem. Sometimes it takes 6-15 for the home page to open, after that it's super fast.

How can I trace DNS query, lookup time, etc, etc on Windows 7, Windows server running DNS service or linux box setup with ubuntu, or any other tool out there?

Thank you
0
Comment
Question by:Coffinated
  • 2
4 Comments
 
LVL 20

Accepted Solution

by:
brwwiggins earned 250 total points
ID: 35012632
You can do a simple DIG or NSLOOKUP from a client and see if it is a DNS issue. If the DNS server returns the IP address immediately you can pretty much rule it out.

Is this a .NET app? Sometimes .NET apps run slow initially because they must be compiled if they are not resident in the app pool memory. There are ways you can pre-compile apps to avoid this delay.
0
 
LVL 5

Author Comment

by:Coffinated
ID: 35012726
It's a Joomla based website set up on fairly fast VPS. I did create a clone on much slower server and it opens instantly. not sure what the problem is, server load is low, ping very low, DNS was the last thing to check.
'dig' produced result almost instantly, I'll keep checking it when site loads slowly again.
0
 
LVL 5

Assisted Solution

by:group0
group0 earned 250 total points
ID: 35031846
It sounds like a nameserver being hit somewhere in the recursive lookup is not responding, so it has to wait for a timeout before using a secondary NS to continue the lookup.  Once the final record is in your local resolver's cache, it'll continue to be quick until the TTL expires.

To bypass any caching on the part of your local resolver, use:

dig +trace www.domain.com

This will do a fresh recursive lookup each time (although other DNS servers in the chain may still cache their results).  If it pauses during the output, you'll have a good idea of which set of nameservers is the problem.  Then you can do a manual dig against each one until you find out which one is failing, eg:

dig www.domain.com @ns1.domain.com
dig www.domain.com @ns2.domain.com
0
 
LVL 5

Author Comment

by:Coffinated
ID: 35158659
The problem was related to underlying hardware, it disappeared once VPS got moved to another host.
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Redirected folders in a windows domain can be quite useful for a number of reasons, one of them being that with redirected application data, you can give users more seamless experience when logging into different workstations.  For example, if a use…
I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

705 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

18 Experts available now in Live!

Get 1:1 Help Now