The flushdns gets rid of any resolves at the computer level
Code:
Microsoft Windows [Version 10.0.17134.765](c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\john>ipconfig /flushdns
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\john>
If anything is hung up in there, this will clear it.
The tracert (Trace Route) will tell you what route the person's computer takes to get to thesite.com. In the example below, you'll see that zencart.com must first be resolved to its IP. Then, the system tells you what route it takes to get there. You'll first need to check that the IP that thesite.com resolves to is the correct IP for the actual site.
Code:
Microsoft Windows [Version 10.0.17134.765](c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\john>tracert zencart.com
Tracing route to zencart.com [104.236.245.70]
over a maximum of 30 hops:
1 2 ms 2 ms 1 ms READYSHARE [192.168.1.1]
2 4 ms 3 ms 4 ms 10.31.0.1
3 3 ms 4 ms 4 ms 38.142.208.146
4 6 ms 5 ms 5 ms 38.142.208.145
5 11 ms 10 ms 10 ms be2292.ccr42.iah01.atlas.cogentco.com [154.54.1.81]
6 11 ms 11 ms 12 ms be3486.rcr22.iah02.atlas.cogentco.com [154.54.30.166]
7 13 ms 11 ms 12 ms be3632.nr51.b023723-0.iah02.atlas.cogentco.com [154.24.45.58]
8 14 ms 15 ms 14 ms telia.iah02.atlas.cogentco.com [154.54.12.78]
9 29 ms 29 ms 30 ms atl-b24-link.telia.net [62.115.116.47]
10 30 ms 29 ms 31 ms atl-b22-link.telia.net [62.115.113.24]
11 49 ms 48 ms 49 ms ash-bb3-link.telia.net [62.115.125.190]
12 46 ms 46 ms 46 ms nyk-bb3-link.telia.net [62.115.141.245]
13 48 ms 49 ms 51 ms nyk-b3-link.telia.net [62.115.140.223]
14 49 ms 48 ms 49 ms digitalocean-ic-306497-nyk-b3.c.telia.net [62.115.45.6]
15 * * * Request timed out.
16 49 ms 49 ms 49 ms 104.236.245.70
Trace complete.
C:\Users\john>
A "Request timed out." Is generally not a problem. What we want to see is the "Trace complete" going to the correct IP.
Bookmarks