[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-20。"],[[["\u003cp\u003eCNAME chasing is the process where a DNS resolver performs a subsequent lookup of a DNS name returned from a CNAME record.\u003c/p\u003e\n"],["\u003cp\u003eWhen Google Cloud VMs use the metadata server as their name server, Cloud DNS will follow specific CNAME chasing rules based on the source of the CNAME answer.\u003c/p\u003e\n"],["\u003cp\u003eCloud DNS performs queries for CNAME answers within its private zones if those zones have local records and are authorized for the VPC network, but does not check public DNS zones.\u003c/p\u003e\n"],["\u003cp\u003eCloud DNS does not perform queries for CNAME answers received from forwarding target name servers or from response policy zones.\u003c/p\u003e\n"],["\u003cp\u003eCloud DNS will query both the internal DNS service and public zones, including its own public zones, when the CNAME answer is sourced from a Cloud DNS public zone, but does not perform queries for private zones in this scenario.\u003c/p\u003e\n"]]],[],null,["# CNAME chasing refers to a subsequent lookup of a DNS name returned from a CNAME\nrecord answer to an initial query. Public DNS resolvers perform subsequent\nlookup of CNAME answers according to their configuration. Generally, public\nresolvers chase CNAME answers in any public zones.\n\nWhen Google Cloud VMs use their metadata server (`169.254.169.254`) as\ntheir name server, and no alternative name server is defined in an outbound\nserver policy of the VPC network, Cloud DNS performs\nCNAME chasing as described in the following table.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nWhat's next\n-----------\n\n- To find solutions for common issues that you might encounter when using Cloud DNS, see [Troubleshooting](/dns/docs/troubleshooting)."]]
