vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/cce/umn/cce_bestpractice_0353.html
Dong, Qiu Jian f7b9a88535 CCE UMN update -20240625 version 
Reviewed-by: Kovács, Zoltán <zkovacs@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
2024-09-04 11:43:54 +00:00

1.4 KiB
Raw Permalink Blame History

Adjusting the DNS Configuration of the VPC and VM

When the coredns add-on is started, it obtains the DNS configuration in the resolve.conf file from the deployed instance by default and uses the configuration as the upstream resolution server address. Before the coredns add-on is restarted, the resolve.conf configuration on the node is not reloaded. Suggestions:

  • Ensure that the resolve.conf configuration of each node in the cluster is the same. In this way, the coredns add-on can schedule requests to any node in the cluster.
  • When modifying the resolve.conf file, if the node has a coredns add-on, restart the coredns add-on timely to ensure status consistency.
Parent topic: Client