Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
troubleshooting:testing-dns-using-nslookup [2010-08-02 17:28:33] garrett.plasky created |
troubleshooting:testing-dns-using-nslookup [2010-08-02 17:42:11] garrett.plasky |
||
---|---|---|---|
Line 3: | Line 3: | ||
=====What is NSlookup? | =====What is NSlookup? | ||
NSlookup is a utility that allows users to verify that a given domain name (or domain record) is resolving properly locally on their PC. It is also useful to check DNS caching, to ensure that after a DNS changeover that the PC is seeing the new IP address entry. | NSlookup is a utility that allows users to verify that a given domain name (or domain record) is resolving properly locally on their PC. It is also useful to check DNS caching, to ensure that after a DNS changeover that the PC is seeing the new IP address entry. | ||
- | |||
=====Using NSlookup===== | =====Using NSlookup===== | ||
To access nslookup on a Windows workstation, | To access nslookup on a Windows workstation, | ||
Line 13: | Line 12: | ||
{{ : | {{ : | ||
- | |||
=====Interpreting Results===== | =====Interpreting Results===== | ||
- | The first column, the hop count, represents the number of stops your information has made along the route to attempt to contact | + | Of particular interest |
- | + | ||
- | The above example shows a successful trace without any unreachable hosts. If your trace dies out after a specific hop by only returning full lines of asterisks ("* * * *"), then chances are the issue is at or just after the hop before | + | |
- | Large jumps in response times can also mean a possible issue. If you are consistently seeing around 5ms for your first 3 hops, for example, and then on the 4th hop the response time jumps to 500ms, then there may be an issue with the 4th hop. | + | If the domain' |
=====Sending Us the Results===== | =====Sending Us the Results===== |