Google DNS server do not return a nearest IP address for Yahoo Hong Kong

[Jean]

Hello,
I have an Internet user from Hong Kong. I have been using Google
Public DNS for a period. Google Public DNS can resolve the nearest IP
address most of time for website utilize CDN.
However, for Yahoo Hong Kong site (hk.yahoo.com), Google Public DNS
could not resolve the IP address of the nearest server. The situation
is listed as belows:

C:\Users\Jean>nslookup hk.yahoo.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name: any-ycpi-uno.aycpi.b.yahoodns.net
Addresses: 208.71.44.30
98.139.126.21
208.71.44.31
98.139.126.20
67.195.141.200
67.195.141.201
Aliases: hk.yahoo.com
geoycpi-uno.gycpi.b.yahoodns.net

C:\Users\Jean>ping -n 1 208.71.44.30
Pinging 208.71.44.30 with 32 bytes of data:
Reply from 208.71.44.30: bytes=32 time=200ms TTL=50
Ping statistics for 208.71.44.30:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 200ms, Maximum = 200ms, Average = 200ms
C:\Users\Jean>ping -n 1 98.139.126.21
Pinging 98.139.126.21 with 32 bytes of data:
Reply from 98.139.126.21: bytes=32 time=176ms TTL=53
Ping statistics for 98.139.126.21:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 176ms, Maximum = 176ms, Average = 176ms
C:\Users\Jean>ping -n 1 208.71.44.31
Pinging 208.71.44.31 with 32 bytes of data:
Reply from 208.71.44.31: bytes=32 time=197ms TTL=50
Ping statistics for 208.71.44.31:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 197ms, Maximum = 197ms, Average = 197ms
C:\Users\Jean>ping -n 1 98.139.126.20
Pinging 98.139.126.20 with 32 bytes of data:
Reply from 98.139.126.20: bytes=32 time=175ms TTL=53
Ping statistics for 98.139.126.20:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 175ms, Maximum = 175ms, Average = 175ms
C:\Users\Jean>ping -n 1 67.195.141.200
Pinging 67.195.141.200 with 32 bytes of data:
Reply from 67.195.141.200: bytes=32 time=175ms TTL=53

Ping statistics for 67.195.141.200:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 175ms, Maximum = 175ms, Average = 175ms
C:\Users\Jean>ping -n 1 67.195.141.201
Pinging 67.195.141.201 with 32 bytes of data:
Reply from 67.195.141.201: bytes=32 time=175ms TTL=53
Ping statistics for 67.195.141.201:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 175ms, Maximum = 175ms, Average = 175ms

Nevertheless, other public DNS service that also set nodes in Hong
Kong, such as DNS Advantage and Norton DNS do not have this problem
for Yahoo Hong Kong (hk.yahoo.com). The result gathered from other DNS
are listed as the follows: (DNS Advantage as an example)

C:\Users\Jean>nslookup hk.yahoo.com 156.154.71.1
Server: rdns2.ultradns.net
Address: 156.154.71.1
Non-authoritative answer:
Name: hki-ycpi-uno.gycpi.b.yahoodns.net
Addresses: 124.108.82.79
124.108.82.78
Aliases: hk.yahoo.com
geoycpi-uno.gycpi.b.yahoodns.net
fo-hki-ycpi-uno.gycpi.b.yahoodns.net
C:\Users\Jean>ping -n 1 124.108.82.79
Pinging 124.108.82.79 with 32 bytes of data:
Reply from 124.108.82.79: bytes=32 time=2ms TTL=55
Ping statistics for 124.108.82.79:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms
C:\Users\Jean>ping -n 1 124.108.82.78
Pinging 124.108.82.78 with 32 bytes of data:
Reply from 124.108.82.78: bytes=32 time=6ms TTL=55
Ping statistics for 124.108.82.78:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 6ms, Average = 6ms

This problem is inconvenience to Hong Kong users. For one thing, Yahoo
Hong Kong is a famous portal to Hong Konger. For another, Google
Public DNS is a must for some ISPs user that DNSs of ISP have been
hijacked.

Is the issue only found for Yahoo Hong Kong site? Could the problem be
solved?

Jean