qcomgeo2.com - getting NXDOMAIN for queries from Taipei

[Puneet Sood]

Hello,

We are seeing this problem when resolving openid.qualcomm.com from our
resolvers in Taipei. Resolvers in other nearby locations (e.g.
Singapore and Sydney) are not seeing this problem. FWIW
http://dnsviz.net/d/qcomgeo2.com/dnssec/ reports inconsistency in the
authoritative nameservers and those reported in the delegation from
COM zone.

A successful resolution results in the following chain.

$ dig @8.8.8.8 openid.qualcomm.com +dnssec +short
;; ANSWER SECTION:
openid.qualcomm.com.    3599    IN      CNAME   openid.qcomgeo2.com.
openid.qcomgeo2.com.    21599   IN      CNAME
secure6.qualcomm.com.edgekey.net.
secure6.qualcomm.com.edgekey.net. 21599 IN CNAME e1479.dscx.akamaiedge.net.
e1479.dscx.akamaiedge.net. 19   IN      A       104.110.192.201

However from our Taipei data centers the resolution stops at the first
CNAME with an NXDOMAIN for openid.qcomgeo2.com.

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25009
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

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

;; ANSWER SECTION:
openid.qualcomm.com.    3599    IN      CNAME   openid.qcomgeo2.com.

;; AUTHORITY SECTION:
qcomgeo2.com.           1799    IN      SOA     a1.verisigndns.com.
mdnshelp.verisign.com. 1497463589 28800 7200 1209600 86400

;; Query time: 75 msec
;; SERVER: 2002:abd:cb12::#53(2002:abd:cb12::)
;; WHEN: Thu Aug 22 13:14:56 PDT 2019
;; MSG SIZE  rcvd: 147

What is special for Google Public DNS egress IPs in Taipei?

The egress ranges we use in Taipei (from
https://developers.google.com/speed/public-dns/faq#locations).
74.125.41.0/24 tpe
172.217.42.0/24 tpe
173.194.93.0/24 tpe
173.194.171.0/24 tpe
2404:6800:4008::/48 tpe

Thanks,
Puneet