Incorrect IP locating for 182.61.64.0/19

[rss...@gmail.com]

To Google public DNS maintainers:
Address block 182.61.64.0/19 is reassigned to its Hong Kong IDC by Baidu, which is a China Internet company.
But Google still recognize the addresses as China, which seems causing recursive resolvings like Google, YouTube, Facebook never hitting their HK nodes.
Can you guys help to mark 182.61.64.0/19 as Hong Kong?

Thanks!

[Shen Wan]

I am not sure this is a DNS problem. What do you mean recursive resolving? Could you show me the domain in question and your query results against 8.8.8.8?

[Alex Dupuy]

Address block 182.61.64.0/19 is reassigned to its Hong Kong IDC by Baidu, which is a China Internet company.

Can you guys help to mark 182.61.64.0/19 as Hong Kong?

The GeoIP databases are not part of Google Public DNS, so we can't update this ourselves.  If you want those to be updated, you should fill out a request form at https://support.google.com/websearch/contact/ip (I found this through https://support.google.com/websearch/answer/873).

Please provide specific evidence that this netblock has been reassigned to HK-based ISP or subsidiary, especially as WHOIS and all other GeoIP databases that I could find show this block as located in China.

http://wq.apnic.net/apnic-bin/whois.pl?searchtext=182.61.64.0

http://whatismyipaddress.com/ip/182.61.64.0

https://www.iplocation.net/ (you have to enter the IP on the form at that page)

You will probably want to submit updates to the other GeoIP databases (MaxMind, ipinfo.io etc.) as well, since many other services would have this same problem.

[Shen Wan]

Could you run these commands?

dig +short @8.8.8.8 o-o.myaddr.l.google.com txt

nslookup -type=TXT o-o.myaddr.l.google.com 8.8.8.8

On Wed, Feb 24, 2016 at 11:20 PM, Justin <rss...@gmail.com> wrote:

Hi Shen and all,

This looks an interesting issue that I'd like to share some details. 

My IP address is 182.61.64.142, and here's the BGP announces of block 182.61.64.0/18 (not /19, my bad :) )  : http://bgp.he.net/net/182.61.64.0/18  , AS55967 is located in HK.

Also, you can use some approaches like ping latency or traceroute to detect its location.

And here are Some of my tests:

1. Resolve Facebook, YouTube on my Hong Kong server using 8.8.8.8, and you can see they resolve to America and Taiwan, not in HK:

​

2. Detect the DNS recursion IP of 8.8.8.8 using my self-hosted authoritative DNS server, and you can see the query is coming from a Taiwan IP:

​

BTW, here's a very good GeoIP database: https://www.ipip.net/?l=EN

It is developed by a Chinese startup company using BGP and traceroute methods, which make it more precise than any other published GeoIP databases.

Best Regards,

-Justin

[Justin]

Hi Shen and all,

This looks an interesting issue that I'd like to share some details. 

My IP address is 182.61.64.142, and here's the BGP announces of block 182.61.64.0/18 (not /19, my bad :) )  : http://bgp.he.net/net/182.61.64.0/18  , AS55967 is located in HK.

Also, you can use some approaches like ping latency or traceroute to detect its location.

And here are Some of my tests:

1. Resolve Facebook, YouTube on my Hong Kong server using 8.8.8.8, and you can see they resolve to America and Taiwan, not in HK:

​

2. Detect the DNS recursion IP of 8.8.8.8 using my self-hosted authoritative DNS server, and you can see the query is coming from a Taiwan IP:

​

BTW, here's a very good GeoIP database: https://www.ipip.net/?l=EN

It is developed by a Chinese startup company using BGP and traceroute methods, which make it more precise than any other published GeoIP databases.

Best Regards,

-Justin

On Wed, Feb 24, 2016 at 11:11 PM, Shen Wan <she...@google.com> wrote:

[Justin]

Done.

root@bce-hk:~# dig +short @8.8.8.8 o-o.myaddr.l.google.com txt

"74.125.41.65"

"edns0-client-subnet 182.61.64.0/24"

root@bce-hk:~# nslookup -type=TXT o-o.myaddr.l.google.com 8.8.8.8

Server:         8.8.8.8

Address:        8.8.8.8#53

Non-authoritative answer:

o-o.myaddr.l.google.com text = "173.194.93.10"

o-o.myaddr.l.google.com text = "edns0-client-subnet 182.61.64.0/24"

Authoritative answers can be found from:

root@bce-hk:~#

[Shen Wan]

Your result shows that Google Public DNS sends the correct ECS option to ns?.google.com. And indeed ns?.google.com returns Taiwan IP for www.youtube.com:

So this is not a DNS resolving issue. Have you tried Alex's suggestions?

; <<>> DiG 9.10.2 <<>> +norec +subnet=182.61.64.0/24 www.youtube.com @ns1.google.com

;; global options: +cmd

;; Got answer:

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

;; flags: qr aa; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

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

; CLIENT-SUBNET: 182.61.64.0/24/17

;; QUESTION SECTION:

;www.youtube.com.               IN      A

;; ANSWER SECTION:

www.youtube.com.        86400   IN      CNAME   youtube-ui.l.google.com.

youtube-ui.l.google.com. 900    IN      CNAME   youtube-ui-china.l.google.com.

youtube-ui-china.l.google.com. 180 IN   A       173.194.72.100

youtube-ui-china.l.google.com. 180 IN   A       173.194.72.102

youtube-ui-china.l.google.com. 180 IN   A       173.194.72.138

youtube-ui-china.l.google.com. 180 IN   A       173.194.72.113

youtube-ui-china.l.google.com. 180 IN   A       173.194.72.101

youtube-ui-china.l.google.com. 180 IN   A       173.194.72.139