Locally, on a "Home" network, performing a "tracert" to a known Computer Name also located on the Home network, the route returned should be rather short, correct?
So if the tracert goes off and begins displaying a route return that appears to go overseas (departing U.S. through "barefruit.co.uk
") this is NOT the proper and/or desireable return, right? "Barefruit" is the last discernible named device showing in the 'tracert' and it is presumably based in "sanjose" (California, US) as indicated in the readout.
My concerns include the computer(s) in question, or possibly the network, having had some undesirable software of one type or another "injected" onto it. Routinely there are two (2) computers on the Home network in question. Occasionally a third Linux desktop computer may be used, and there are also 4 or 5 Android-based devices utilizing the same Wi-Fi router and uplink provided by COX communications.
Clearly my networking knowledge is a bit "behind the times" and maybe there is MORE to DNS these days than I understand, if so I would appreciate the briefest of explanations on why a "tracert" should behave in this manner.
If this sort of 'tracert' return is "normal" that is fine, I am just curious whether ANY of the systems connected to the local network might need to be COMPLETELY wiped and reloaded.
Thanks very much in advance!