Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
troubleshooting:testing-dns-using-nslookup [2010-08-02 17:41:21]
garrett.plasky 		troubleshooting:testing-dns-using-nslookup [2010-08-02 17:42:11] (current)
garrett.plasky
Line 12: Line 12:
  
 {{ :troubleshooting:nslookup.png?200&direct |NSlookup Results}} {{ :troubleshooting:nslookup.png?200&direct |NSlookup Results}}
- 
 =====Interpreting Results===== =====Interpreting Results=====
-Of particular interest to us is the //Address// field listed in the **Non-authoratative answer** section. This displays the IP that the domain name queried resolves to on the workstation locally. If the workstation is having DNS issues, this answer may come up blank.+Of particular interest to us is the //Address// field listed in the **Non-authoratative answer** section. This displays the IP that the domain name queried resolves to on the workstation locally. If the workstation is having DNS issues, this answer may come up blank. If an IP is returned, this should match the IP configured on the server on which the domain resides.
  
 If the domain's A record was recently updated the IP may be cached at the workstation's local resolver and the IP listed may differ from the new one. If this is the case, the PCs cache can be cleared forcing it to look to it's local resolver for the new record. This is done using the command //ipconfig /flushdns// from the same command prompt window the nslookup was run in. Note that this will only clear the workstation's cache and not the local DNS server(s), so if those have not been updated with the new record yet, this command will not have any effect. If the domain's A record was recently updated the IP may be cached at the workstation's local resolver and the IP listed may differ from the new one. If this is the case, the PCs cache can be cleared forcing it to look to it's local resolver for the new record. This is done using the command //ipconfig /flushdns// from the same command prompt window the nslookup was run in. Note that this will only clear the workstation's cache and not the local DNS server(s), so if those have not been updated with the new record yet, this command will not have any effect.