Because the site just moved, I’ve been watching Google’s notifications and indexing status these days, but found that 38% of the errors are domain resolution errors — Google cannot resolve the domain. Then I searched and found this isn’t an偶然 (isolated) phenomenon; all DNSpod free users have had the problem of Google being unable to resolve, and I also found @奶罩’s (NaiZhao’s) reply.
It’s like this: the resolution server is either domestic or overseas. DNSpod also has two versions, a domestic version and an international version. The international version Google can definitely resolve, but domestic users suffer — using the domestic version causes the Google-can’t-resolve problem. You can’t have both fish and bear’s paw.
The only solution is to buy the paid resolution service; they have overseas resolution nodes that take care of both domestic and overseas users, and Google can resolve too.
It’s a pity I can’t afford it — you can only get one of the fish and the bear’s paw. Other companies have more DNS servers and more computer rooms.