Google DNS resolve wrong GeoLocation

noc...@gmail.com

unread,

Oct 16, 2018, 8:51:23 AM10/16/18

to public-dns-discuss

Hi

When we use UltraDNS Geo function from an Taiwan IP against 8.8.8.8 that it will resolve 2 different CNAMES one as 2lqz53q.x.haoli443.com. which is the correct setting for Taiwan, but the others times it will will resolve as cdn.haoli443.com.cdn.dnsv1.com. (China)

Do you know the reason why we are seeing this problem?

Administrator@NOC-Office-PC ~

$ dig @8.8.8.8 cdn.haoli443.com

; <<>> DiG 9.11.2-P1 <<>> @8.8.8.8 cdn.haoli443.com

; (1 server found)

;; global options: +cmd

;; Got answer:

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

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

;; OPT PSEUDOSECTION:

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

;; QUESTION SECTION:

;cdn.haoli443.com. IN A

;; ANSWER SECTION:

cdn.haoli443.com. 595 IN CNAME 2lqz53q.x.haoli443.com.

2lqz53q.x.haoli443.com. 595 IN CNAME 2lqz53q.x.incapdns.net.

2lqz53q.x.incapdns.net. 25 IN A 107.154.197.159

;; Query time: 22 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: 週二十月 16 16:35:48 CST 2018

;; MSG SIZE rcvd: 121

Administrator@NOC-Office-PC ~

$ dig @8.8.8.8 cdn.haoli443.com

; <<>> DiG 9.11.2-P1 <<>> @8.8.8.8 cdn.haoli443.com

; (1 server found)

;; global options: +cmd

;; Got answer:

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

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

;; OPT PSEUDOSECTION:

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

;; QUESTION SECTION:

;cdn.haoli443.com. IN A

;; ANSWER SECTION:

cdn.haoli443.com. 551 IN CNAME cdn.haoli443.com.cdn.dnsv1.com.

cdn.haoli443.com.cdn.dnsv1.com. 599 IN CNAME 776559.dispatch.spcdntip.com.

776559.dispatch.spcdntip.com. 59 IN A 182.118.11.126

776559.dispatch.spcdntip.com. 59 IN A 101.69.121.19

776559.dispatch.spcdntip.com. 59 IN A 122.143.6.39

776559.dispatch.spcdntip.com. 59 IN A 43.242.166.88

776559.dispatch.spcdntip.com. 59 IN A 27.221.28.231

776559.dispatch.spcdntip.com. 59 IN A 1.189.213.64

776559.dispatch.spcdntip.com. 59 IN A 42.236.125.84

776559.dispatch.spcdntip.com. 59 IN A 113.200.16.234

776559.dispatch.spcdntip.com. 59 IN A 221.204.166.70

776559.dispatch.spcdntip.com. 59 IN A 113.1.0.33

776559.dispatch.spcdntip.com. 59 IN A 101.69.121.24

776559.dispatch.spcdntip.com. 59 IN A 125.211.204.252

776559.dispatch.spcdntip.com. 59 IN A 113.1.0.34

776559.dispatch.spcdntip.com. 59 IN A 116.95.25.196

776559.dispatch.spcdntip.com. 59 IN A 122.143.6.38

;; Query time: 361 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: 週二十月 16 16:35:49 CST 2018

;; MSG SIZE rcvd: 365

noc...@gmail.com

unread,

Oct 16, 2018, 11:23:44 AM10/16/18

to public-dns-discuss

Maybe this information can help you find the root cause of the problem. We did not have this problem at all prior to September 19th. I hope this helps.

Alex Dupuy

unread,

Oct 17, 2018, 8:57:12 AM10/17/18

to public-dns-discuss

When we use UltraDNS Geo function from an Taiwan IP against 8.8.8.8 that it will resolve 2 different CNAMES one as 2lqz53q.x.haoli443.com. which is the correct setting for Taiwan, but the others times it will will resolve as cdn.haoli443.com.cdn.dnsv1.com. (China)

Do you know the reason why we are seeing this problem?

Google Public DNS monitoring shows that we are sending EDNS Client Subnet for all queries to the UltraDNS name servers.

Do you get the same results with repeated queries from 8.8.4.4 or from OpenDNS?

dig @8.8.4.4 cdn.haoli443.com

dig @resolver1.opendns.com cdn.haoli443.com

If you see the same problems with OpenDNS, there is an issue at the UltraDNS side.

If both 8.8.4.4 and OpenDNS work correctly, perhaps some of your traffic to 8.8.8.8 is being hijacked? What do you see when you repeatedly query

dig -t TXT @8.8.8.8 test.dns.google.com

noc...@gmail.com

unread,

Oct 17, 2018, 10:50:29 AM10/17/18

to public-dns-discuss

Hi Alex

8.8.4.4 work not correctly,OpenDNS work correctly ,

We found that only 8.8.8.8 and 8.8.4.4 have this problem ,did not have this problem at prior to September 19th,
other public DNS in Taiwan is work correctly.

result

Administrator@NOC-Office-PC ~
$ dig @resolver1.opendns.com cdn.haoli443.com

; <<>> DiG 9.11.2-P1 <<>> @resolver1.opendns.com cdn.haoli443.com

; (1 server found)
;; global options: +cmd
;; Got answer:

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

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

;; OPT PSEUDOSECTION:

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

;; QUESTION SECTION:
;cdn.haoli443.com. IN A

;; ANSWER SECTION:

cdn.haoli443.com.       599     IN      CNAME   2lqz53q.x.haoli443.com.
2lqz53q.x.haoli443.com. 599     IN      CNAME   2lqz53q.x.incapdns.net.
2lqz53q.x.incapdns.net. 29      IN      A       107.154.197.159

;; Query time: 70 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: 週三十月 17 22:31:18 CST 2018

;; MSG SIZE rcvd: 121

Administrator@NOC-Office-PC ~
$

Administrator@NOC-Office-PC ~
$ dig @8.8.4.4 cdn.haoli443.com

; <<>> DiG 9.11.2-P1 <<>> @8.8.4.4 cdn.haoli443.com

; (1 server found)
;; global options: +cmd
;; Got answer:

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

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;cdn.haoli443.com. IN A

;; ANSWER SECTION:

cdn.haoli443.com. 352 IN CNAME cdn.haoli443.com.cdn.dnsv1.com.

cdn.haoli443.com.cdn.dnsv1.com. 599 IN CNAME 776559.dispatch.spcdntip.com.

776559.dispatch.spcdntip.com. 59 IN     A       1.189.213.64
776559.dispatch.spcdntip.com. 59 IN     A       42.236.125.84
776559.dispatch.spcdntip.com. 59 IN     A       113.200.16.234
776559.dispatch.spcdntip.com. 59 IN     A       221.204.166.70
776559.dispatch.spcdntip.com. 59 IN     A       113.1.0.33
776559.dispatch.spcdntip.com. 59 IN     A       101.69.121.24
776559.dispatch.spcdntip.com. 59 IN     A       125.211.204.252
776559.dispatch.spcdntip.com. 59 IN     A       113.1.0.34
776559.dispatch.spcdntip.com. 59 IN     A       116.95.25.196
776559.dispatch.spcdntip.com. 59 IN     A       122.143.6.38

776559.dispatch.spcdntip.com. 59 IN A 182.118.11.126

776559.dispatch.spcdntip.com. 59 IN A 27.221.28.231

776559.dispatch.spcdntip.com. 59 IN A 122.143.6.39
776559.dispatch.spcdntip.com. 59 IN A 101.69.121.19

776559.dispatch.spcdntip.com. 59 IN A 43.242.166.88

;; Query time: 64 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: 週三十月 17 22:31:22 CST 2018
;; MSG SIZE rcvd: 365

Administrator@NOC-Office-PC ~
$

noc...@gmail.com

unread,

Oct 17, 2018, 11:13:05 AM10/17/18

to public-dns-discuss

Hi Alex

Please kindly refer to the information you are looking for in the video below

https://youtu.be/T_V-IbEhHl0

you can see only 8.8.8.8 and 8.8.4.4 not work correctly , other public DNS is work correctly

Alex Dupuy

unread,

Oct 17, 2018, 11:23:52 AM10/17/18

to public-dns-discuss

Followup on this at https://issuetracker.google.com/issues/117855684

noc...@gmail.com

unread,

Nov 5, 2018, 10:09:15 PM11/5/18

to public-dns-discuss

hi Alex

No one answered, the current problem has not improved.

Alex Dupuy於 2018年10月17日星期三 UTC+8下午11時23分52秒寫道：

noc...@gmail.com

unread,

Nov 5, 2018, 10:15:36 PM11/5/18

to public-dns-discuss

Hi
can you try other domain "cdn.cxdjh.com"

from Taiwan test(ip 202.133.244.126) , current answer must 35.194.138.236(ECS=Taiwan) , but sometime answer is wrong answer (ECS=China)

$ dig @8.8.8.8 cdn.cxdjh.com

; <<>> DiG 9.11.2-P1 <<>> @8.8.8.8 cdn.cxdjh.com

; (1 server found)
;; global options: +cmd
;; Got answer:

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

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:

;cdn.cxdjh.com.                 IN      A

;; ANSWER SECTION:
cdn.cxdjh.com.          353     IN      CNAME   cdn.cxdjh.com.cdn.dnsv1.com.
cdn.cxdjh.com.cdn.dnsv1.com. 592 IN     CNAME   1015463.dispatch.spcdntip.com.
1015463.dispatch.spcdntip.com. 52 IN    A       113.200.16.234
1015463.dispatch.spcdntip.com. 52 IN    A       113.200.16.98
1015463.dispatch.spcdntip.com. 52 IN    A       221.204.166.70
1015463.dispatch.spcdntip.com. 52 IN    A       101.69.121.24
1015463.dispatch.spcdntip.com. 52 IN    A       101.69.121.19
1015463.dispatch.spcdntip.com. 52 IN    A       122.143.6.38
1015463.dispatch.spcdntip.com. 52 IN    A       27.221.54.252
1015463.dispatch.spcdntip.com. 52 IN    A       122.143.6.39
1015463.dispatch.spcdntip.com. 52 IN    A       116.95.25.196
1015463.dispatch.spcdntip.com. 52 IN    A       113.1.0.34
1015463.dispatch.spcdntip.com. 52 IN    A       110.53.180.248
1015463.dispatch.spcdntip.com. 52 IN    A       113.1.0.33
1015463.dispatch.spcdntip.com. 52 IN    A       125.211.204.252
1015463.dispatch.spcdntip.com. 52 IN    A       43.242.166.88
1015463.dispatch.spcdntip.com. 52 IN    A       1.189.213.64

;; Query time: 7 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 06 11:11:58 CST 2018
;; MSG SIZE rcvd: 360

SITMN17+Administrator@SITMN17 ~
$ dig @8.8.8.8 cdn.cxdjh.com

; <<>> DiG 9.11.2-P1 <<>> @8.8.8.8 cdn.cxdjh.com

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11600
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:

;cdn.cxdjh.com.                 IN      A

;; ANSWER SECTION:
cdn.cxdjh.com.          599     IN      CNAME   cdn-t1.cxdjh.com.
cdn-t1.cxdjh.com.       599     IN      A       35.194.138.236

;; Query time: 14 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 06 11:12:00 CST 2018
;; MSG SIZE rcvd: 79

SITMN17+Administrator@SITMN17 ~
$

Alex Dupuy於 2018年10月17日星期三 UTC+8下午11時23分52秒寫道：

Reply all

Reply to author

Forward