Unbound's CNAME chasing causing Microsoft domains resovled to abroad CDN

[sorz]

Unbound's CNAME chasing causing Microsoft domains resovled to abroad CDN

[felixonmars]

• Does intermediate CDN domains qualified to be in the list?

Yes, and they already do (you can find many apple's akadns target in apple.china.conf, for example). Some of them even come from the time when I use unbound myself. I generally accept submissions for them but as long as I use dnsmasq or smartdns, I don't need it myself and won't be able to observe more instances like this. I'll still be accepting these contributions.

• If yes, in which level of such domains should be in the list, www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net., edgekey.net.globalredir.akadns.net., or even broader one?

To be on the safe side, I would prefer to maintain only www.microsoft.com-c-3.edgekey.net.globalredir.akadns.net. level aliases as they can be easily verified and (semi) auto-removed when they are no longer applicable.

[sorz]

How about www.microsoft.com-c-3.edgekey.net.? It doesn't meet neither of the two criteria so we leave them out?

[felixonmars]

No, it's also the direct CNAME target of www.microsoft.com and could be included as well.

[sorz]

Oh yes, the criteria of "resolving to mainland China IPs in China but not outside China" goes for the final A records, not for the intermediate CNAME records.