Improve company productivity with a Business Account.Sign Up

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

Trace DNS query and lookup time

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
Coffinated
Asked:
Coffinated
  • 2
2 Solutions
 
brwwigginsIT ManagerCommented:
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
 
CoffinatedAuthor Commented:
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
 
group0Commented:
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
 
CoffinatedAuthor Commented:
The problem was related to underlying hardware, it disappeared once VPS got moved to another host.
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

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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