Post by VanguardLHPost by D***@MadCow.netnslookup secure.macrium.com
Name: daks4cgsf00ej.cloudfront.net
Addresses: 52.84.64.243
52.84.64.167
52.84.64.150
52.84.64.86
Aliases: secure.macrium.com
Don't know what it means.
nslookup does NOT tell you that you have a route to the actual server
host. All that does is query the nameserver host to equate the hostname
with an IP address. In fact, nslookup never connects to the server
host, only to the nameserver host (yours, or if that fails then the DNS
request gets passed upward in the DNS server chain until it may finally
get to the domain's own nameserver). nslookup will never tell you if a
host if reachable and, if so, if it is responsive.
ping will tell if you can reach the server host and if it is responsive
(if IMCP has not been disabled on the host - not all hosts have ICMP
ping enabled since they don't want to waste the resources on it).
As I mentioned, do a traceroute. What I get is (didn't show the
1 <myModemLANsideIPakaGateway>
2 --.
3 |
4 |
5 |__ hosts to get through my ISP's network
6 |
7 |
8 --'
9 Request timed out.
10 Request timed out.
11 Request timed out.
12 Request timed out.
13 Request timed out.
14 Request timed out.
15 server-13-33-165-48.ord50.r.cloudfront.net [13.33.165.48]
The timeouts are from hosts beyond node 8 that don't respond to pinging.
As a result, my tracert isn't helpful to show what hosts I went through
in my route to the endpoint host (macrium server). It does show that I
could reach THAT host, not some DNS server doling out the IP address for
that hostname.
Don't know if I did it right, but here are the results (on PC #1)
Ping secure.macrium.com
Pinging daks4cgsf00ej.cloudfront.net [13.33.165.48] with 32 bytes of
data:
Reply from 13.33.165.48: bytes=32 time=14ms TTL=246
Reply from 13.33.165.48: bytes=32 time=12ms TTL=246
Reply from 13.33.165.48: bytes=32 time=14ms TTL=246
Reply from 13.33.165.48: bytes=32 time=12ms TTL=246
Ping statistics for 13.33.165.48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 14ms, Average = 13ms
----------------------------------------------
tracert secure.macrium.com
Tracing route to daks4cgsf00ej.cloudfront.net [54.230.51.83]
over a maximum of 30 hops:
1 10 ms 9 ms 9 ms 142.254.152.165
2 9 ms 12 ms 13 ms ae63.nwblwi1802h.midwest.rr.com
[24.164.241.141]
3 14 ms 15 ms 15 ms be63.gnfdwibb01r.midwest.rr.com
[65.31.112.160]
4 14 ms 16 ms 14 ms
bu-ether16.chcgildt87w-bcr00.tbone.rr.com [66.109.6.204]
5 41 ms 40 ms 46 ms
bu-ether11.nycmny837aw-bcr00.tbone.rr.com [66.109.6.24]
6 39 ms 38 ms 38 ms ge-1-3-0.a1.buf00.tbone.rr.com
[66.109.1.57]
7 38 ms 37 ms 39 ms 24.27.236.51
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 48 ms 40 ms 37 ms
server-54-230-51-83.jfk5.r.cloudfront.net [54.230.51.83]
Trace complete.
I'm guessing this is ok, but not pointing to a problem?
DC