Help Center/ Cloud Container Engine/ FAQs/ DNS FAQs/ Why Cannot the Domain Name of the Tenant Zone Be Resolved After the Subnet DNS Configuration Is Modified?

Updated on 2024-07-04 GMT+08:00

View PDF

Why Cannot the Domain Name of the Tenant Zone Be Resolved After the Subnet DNS Configuration Is Modified?

Symptom

After a DNS server record, for example, 114.114.114.114, is added to the DNS configuration of the user cluster subnet, the domain name of the tenant zone cannot be resolved.

Cause Analysis

CCE configures the subnet DNS information of the user on the node, which is also used by the coredns add-on. As a result, the domain name fails to be resolved by the node container occasionally.

Solution

You are advised to modify the stub domain of the coredns add-on to update the DNS configuration of the user cluster subnet. For details, see Configuring the Stub Domain for CoreDNS.

Parent Topic: DNS FAQs

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot