Tracert and IP's

[Scotty.T]

Who knows about the tracert command?

If I run a tracert and everything resolves OK, the final IP address should be the IP the site is hosted on.

What I want to understand is this. If a site is being moved from 1 IP address to another could I get a false reading until all the new stuff propogates across the web?

[A Priest]

my understanding of it is - trace routing an ip tells you that your new server is up and responding on that IP.

DNS (the bit that converts www.myname.com to x.x.x.x) can take a while to propogate the changes around to every dns server.

[adultbusiness]

Depends if you are running a tracert on an IP or Domain Name.... if you tracert to the IP then propogation is not an issue as you are looking at a specific IP (new or old server) but if you tracert the Domain Name then it will resolve to the IP that is associated with the Domain dependant on the propogation being successful.........

[Scotty.T]

Yeah I am running tracert on a domain so the propagation of the DNS will still be an issue I guess.

Thanks.

[A Priest]

there is a handy command called nslookup which you can run from the cmd window.

from what i remember you do:

cmd > nslookup (return)

then type in:

domainname.com (return)

you will get your results from your locally configured primary name server. if you then do:

domainname.com x.x.x.x (return)

where x.x.x.x is the ip of an external dns, you can query that name using a remote dns server.

OR dont be a geek about it, and go to one of countless websites that will do the same for you, much easier.

[johnboy]

It might also be worth running a flushdns command...

Sometimes a bad DNS entry will be cached and you will need to either flush the DNS cache to get rid of it, or wait up to 24 hours for it to be dropped from the cache automatically.

How to Flush DNS in Microsoft Windows
In Microsoft Windows, you can use the command ipconfig /flushdns to flush the DNS resolver cache:

C:\>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.
You can also use the command ipconfig /displaydns to view the DNS resolver cache.

[Scotty.T]

there is a handy command called nslookup which you can run from the cmd window........

How does this differ from tracert? More accurate or just a different way of getting the data.

[Scotty.T]

It might also be worth running a flushdns command...

You can also use the command ipconfig /displaydns to view the DNS resolver cache.

Neither of these 2 work for me.

It's all not too important anyway I was just looking for a quick way to see if the site had changed IP's.