why does I use dig +client to test ,but 8.8.8.8 couldn't return correct answer?

[whic...@gmail.com]

Hi ,

In my LosAngelas machine(70.39.19x.x)，I test as this:

dig 1st.dtwscachev135.ourwebcdn.com @8.8.8.8 +client=210.34.129.13：

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

; CLIENT-SUBNET: 210.34.129.13/32/0

;; QUESTION SECTION:

;1st.dtwscachev135.ourwebcdn.com. IN A

;; ANSWER SECTION:

1st.dtwscachev135.ourwebcdn.com. 119 IN A 115.231.159.126

1st.dtwscachev135.ourwebcdn.com. 119 IN A 115.238.242.107

 

210.34.129.13 is a China IP,it should return :

1st.dtwscachev135.ourwebcdn.com. 119 IN A 163.177.171.114

1st.dtwscachev135.ourwebcdn.com. 119 IN A 60.210.18.63

In my Taiwan-ChungHwaTelecom machine(61.221.18x.x), it can return correct A records,

So ,I don't know what's the difference between these two POPs？Thank you!

Sincerelly

[Shen Wan]

This is because some of our queries to the nameserver 222.163.201.19 are timed out. In that case we may retry queries without ECS option. Please contact the nameserver owner to unblock Google Public DNS's egress IP: https://developers.google.com/speed/public-dns/faq#locations.

[whic...@gmail.com]

Hi Shen Wan,

3q for your reply.

I am the ns owner, I have another domains like:

overseahx.dlmix.speedcdns.com（All ns in region outside China)

1stovcloud.dlmix.mwcdns.com（ns all in region outside China)

apple.xdwscache.ourglb0.com(ns all in China)

It can return correct A records with my test machines' ip, but I didn't get correct answer use dig xxx.com @8.8.8.8 +client=x.x.x.x

For example,

Test machine IP is 1.1.1.1，when I dig with 8.8.8.8 , will return A.A.A.A

if I use +client=2.2.2.2, it will return B.B.B.B

Now, my problem is , whatever IP I changed in "dig +client=", it cannot return B.B.B.B, but always return A.A.A.A.

I even couldn't try it successfully once. So, could you give me more advice? Thank you!

220.243.236.182

在 2016年3月21日星期一 UTC+8下午10:55:18，Shen Wan写道：

[Shen Wan]

I just checked and it works for me:

; <<>> DiG 9.10.2 <<>> +subnet=210.34.129.13/24 1st.dtwscachev135.ourwebcdn.com @8.8.8.8

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61966

;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags:; udp: 512

; CLIENT-SUBNET: 210.34.129.0/24/19

;; QUESTION SECTION:

;1st.dtwscachev135.ourwebcdn.com. IN    A

;; ANSWER SECTION:

1st.dtwscachev135.ourwebcdn.com. 119 IN A       60.210.18.63

1st.dtwscachev135.ourwebcdn.com. 119 IN A       163.177.171.114

;; Query time: 299 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Tue Mar 22 11:49:45 EDT 2016

;; MSG SIZE  rcvd: 103

Which domain do you think 8.8.8.8 returns non-ECS result? What's the result A.A.A.A and the expected result B.B.B.B?

[whic...@gmail.com]

HI ,

Thank you for your reply!

You can dig a correct result, but I can't,  like this:

I don't know what's different between these tests.

能再帮忙看看吗？谢谢您！

在 2016年3月22日星期二 UTC+8下午11:51:24，Shen Wan写道：

[Shen Wan]

Queries to ns[1-5].ourwebcdn.com sometimes time out. It seems that some of your nameservers or the network in between are unstable and may drop queries from us?