Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Trace DNS query and lookup time

Posted on 2011-03-01
4
Medium Priority
?
650 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 1000 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 1000 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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Assume you have an outside contractor who comes in seasonally or once a week to do some work in your office, but you only want to give him access to the programs and files he needs and keep all other documents and programs private. Can you do this o…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
This Micro Tutorial will go in depth within Systems and Security in Windows 7 and will go into detail regarding Action Center, Windows Firewall, System, etc. This will be demonstrated using Windows 7 operating system.
Suggested Courses

810 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