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.
DNS FAQs FAQs
- What Should I Do If Domain Name Resolution Fails?
- Why Does a Container in a CCE Cluster Fail to Perform DNS Resolution?
- Why Cannot the Domain Name of the Tenant Zone Be Resolved After the Subnet DNS Configuration Is Modified?
- How Do I Optimize the Configuration If the External Domain Name Resolution Is Slow or Times Out?
- How Do I Configure a DNS Policy for a Container?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore