cloudfront中国大陆路由跟踪记录

 

1) Do "dig identity.cloudfront.net txt"; or "nslookup -querytype=txt identity.cloudfront.net". This tells us the first DNS server you touch. Some versions of windows may require different parameters to nslookup, but we're looking for something that returns a string such as "ns-lhr3-01.cloudfront.net.lhr3".

输入nslookup -querytype=txt identity.cloudfront.net

C:\Users\liandl>nslookup -querytype=txt identity.cloudfront.net
服务器:  UnKnown
Address:  192.168.2.1

非权威应答:
identity.cloudfront.net text =

        "ns-nrt52-01.cloudfront.net.nrt52"

cloudfront.net  nameserver = ns-02.cloudfront.net
cloudfront.net  nameserver = ns-01.cloudfront.net
ns-01.cloudfront.net    internet address = 207.171.170.1
ns-02.cloudfront.net    internet address = 207.171.179.1

上面的ns-02.cloudfront.net(207.171.170.1 ) ns-01.cloudfront.net(207.171.179.1 )是转CDN域名identity.cloudfront.net为IP的解析用的主辅DNS服务器.

2) Do "dig resolver-identity.cloudfront.net txt"; or "nslookup resolver-identity.cloudfront.net", which tells us your DNS resolver's address.

C:\Users\liandl>nslookup resolver-identity.cloudfront.net
服务器:  UnKnown
Address:  192.168.2.1

非权威应答:
名称:    resolver-identity.cloudfront.net
Address:  218.85.157.4

上面告诉我们,现在的CDN域名resolver-identity.cloudfront.net被我们转成218.85.157.4这个IP.以后我们向resolver-identity.cloudfront.net的请求,都会向218.85.157.4进行网络通信.

3) Do "traceroute d1234.cloudfront.net"; or "tracert d1234.cloudfront.net", where d1234 should be your distribution. This tells us the path being used to your content.

C:\Users\liandl>tracert d3s0zmhu7icjx4.cloudfront.net

通过最多 30 个跃点跟踪
到 d3s0zmhu7icjx4.cloudfront.net [216.137.45.248] 的路由:

  1     1 ms     1 ms    <1 毫秒 192.168.2.1
  2     3 ms     1 ms    <1 毫秒 125.79.176.1
  3     1 ms     1 ms     1 ms  220.162.235.104
  4     3 ms     2 ms     2 ms  61.131.100.225
  5    10 ms    10 ms    10 ms  220.162.233.241
  6    10 ms    10 ms    10 ms  202.97.43.90
  7    26 ms    25 ms    25 ms  202.97.66.149
  8    25 ms    25 ms    25 ms  202.97.33.74
  9    28 ms    27 ms    27 ms  202.97.33.254
 10   166 ms   175 ms   164 ms  202.97.50.2
 11   339 ms   339 ms   341 ms  202.97.49.158
 12   356 ms   412 ms   331 ms  218.30.54.198
 13   335 ms   337 ms   341 ms  los-edge-05.inet.qwest.net [67.14.22.130]
 14   342 ms   342 ms   345 ms  65.113.16.122
 15   260 ms   262 ms   265 ms  server-216-137-45-248.lax1.r.cloudfront.net [216
.137.45.248]

我在China 福建省三明市永安,使用小区电信4MB宽带.

192.168.2.1: 家里无线路由器IP

125.79.176.1:福建省三明市 电信

220.162.235.104 :福建省三明市 电信

61.131.100.225 福建省三明市 电信 福建省南平市 电信

220.162.233.241:福建省三明市 电信

202.97.43.90:中国 电信骨干网

202.97.66.149:甘肃省 电信骨干网

202.97.33.74 :上海市 电信骨干网

202.97.33.254:上海市 电信骨干网

202.97.50.2:中国 电信骨干网

202.97.49.158:中国 电信骨干网

218.30.54.198:中国 电信骨干网 中国电信 美国节点

los-edge-05.inet.qwest.net [67.14.22.130]:美国

65.113.16.122:美国

216 .137.45.248:目的地

下面是连接baidu.com的路由跟踪... 连baidu就是快啊.

C:\Users\liandl>tracert www.baidu.com

通过最多 30 个跃点跟踪
到 www.a.shifen.com [119.75.218.77] 的路由:

  1    <1 毫秒   <1 毫秒   <1 毫秒 192.168.2.1
  2     1 ms     1 ms    <1 毫秒 125.79.176.1
  3     1 ms    <1 毫秒   <1 毫秒 220.162.235.104
  4     4 ms     4 ms     4 ms  61.131.101.225
  5    49 ms     9 ms    11 ms  220.162.234.5
  6    50 ms    50 ms    53 ms  202.97.66.49
  7    45 ms    45 ms    45 ms  220.181.0.42
  8    47 ms    44 ms    44 ms  220.181.0.49
  9    44 ms    44 ms    44 ms  220.181.17.114
 10     *        *        *     请求超时。
 11    45 ms    45 ms    45 ms  119.75.218.77

220.181.17.114:北京市（南三环洋桥电信机房） 电信 北京市 电信

119.75.218.77: 北京市 百度网讯科技

4) Please send us the http headers from when you had a slow retrieval (you can do that from the command line using curl or wget). This gives us transaction ID's we can look at in our logs to verify internal cloudfront performance.
5) How long did the object (from the previous question) take to download?
6) Where (physically) is the computer that is running the test or downloading content? (Frequently an edge location that is physically close will be best, but not always.)
These questions give us a base of data, from which can begin to trouble shoot. It always helps if you can give us an example header when the error is occurring as well.
Thank you,
The CloudFront Team