From 50c0b2901e376be4c644f2d643ecad0e0acbb19a Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Thu, 19 Mar 2026 15:20:49 -0700 Subject: [PATCH] Update dns.md after review Signed-off-by: Sunil Singh --- docs/troubleshooting/other-troubleshooting-tips/dns.md | 2 +- .../current/troubleshooting/other-troubleshooting-tips/dns.md | 2 +- .../troubleshooting/other-troubleshooting-tips/dns.md | 2 +- .../troubleshooting/other-troubleshooting-tips/dns.md | 2 +- .../troubleshooting/other-troubleshooting-tips/dns.md | 2 +- .../troubleshooting/other-troubleshooting-tips/dns.md | 2 +- .../troubleshooting/other-troubleshooting-tips/dns.md | 2 +- .../troubleshooting/other-troubleshooting-tips/dns.md | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/troubleshooting/other-troubleshooting-tips/dns.md b/docs/troubleshooting/other-troubleshooting-tips/dns.md index 9b3dcde419d..b2d8301e22d 100644 --- a/docs/troubleshooting/other-troubleshooting-tips/dns.md +++ b/docs/troubleshooting/other-troubleshooting-tips/dns.md @@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check name resolution issu Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml` for Rancher HA) or are using the embedded kubectl via the UI. -Before running the DNS checks, check the default DNS provider for your cluster and make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) as this can also be the reason why DNS resolution (partly) fails. +Before running the DNS checks, make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) for your DNS provider as this can also be the reason why DNS resolution (partly) fails. ## Check if DNS pods are running diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/troubleshooting/other-troubleshooting-tips/dns.md b/i18n/zh/docusaurus-plugin-content-docs/current/troubleshooting/other-troubleshooting-tips/dns.md index 0c9205d18cd..0b877613274 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/troubleshooting/other-troubleshooting-tips/dns.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/troubleshooting/other-troubleshooting-tips/dns.md @@ -6,7 +6,7 @@ title: DNS 请确保你配置了正确的 kubeconfig（例如，为 Rancher HA 配置了 `export KUBECONFIG=$PWD/kube_config_cluster.yml`）或通过 UI 使用了嵌入式 kubectl。 -在运行 DNS 检查之前，请检查集群的默认 DNS 提供商，并确保[覆盖网络正常运行](networking.md#检查覆盖网络是否正常运行)，因为这也可能导致 DNS 解析（部分）失败。 +Before running the DNS checks, make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) for your DNS provider as this can also be the reason why DNS resolution (partly) fails. ## 检查 DNS pod 是否正在运行 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/troubleshooting/other-troubleshooting-tips/dns.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/troubleshooting/other-troubleshooting-tips/dns.md index 0c9205d18cd..0b877613274 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/troubleshooting/other-troubleshooting-tips/dns.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/troubleshooting/other-troubleshooting-tips/dns.md @@ -6,7 +6,7 @@ title: DNS 请确保你配置了正确的 kubeconfig（例如，为 Rancher HA 配置了 `export KUBECONFIG=$PWD/kube_config_cluster.yml`）或通过 UI 使用了嵌入式 kubectl。 -在运行 DNS 检查之前，请检查集群的默认 DNS 提供商，并确保[覆盖网络正常运行](networking.md#检查覆盖网络是否正常运行)，因为这也可能导致 DNS 解析（部分）失败。 +Before running the DNS checks, make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) for your DNS provider as this can also be the reason why DNS resolution (partly) fails. ## 检查 DNS pod 是否正在运行 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/troubleshooting/other-troubleshooting-tips/dns.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/troubleshooting/other-troubleshooting-tips/dns.md index 0c9205d18cd..0b877613274 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/troubleshooting/other-troubleshooting-tips/dns.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/troubleshooting/other-troubleshooting-tips/dns.md @@ -6,7 +6,7 @@ title: DNS 请确保你配置了正确的 kubeconfig（例如，为 Rancher HA 配置了 `export KUBECONFIG=$PWD/kube_config_cluster.yml`）或通过 UI 使用了嵌入式 kubectl。 -在运行 DNS 检查之前，请检查集群的默认 DNS 提供商，并确保[覆盖网络正常运行](networking.md#检查覆盖网络是否正常运行)，因为这也可能导致 DNS 解析（部分）失败。 +Before running the DNS checks, make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) for your DNS provider as this can also be the reason why DNS resolution (partly) fails. ## 检查 DNS pod 是否正在运行 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/troubleshooting/other-troubleshooting-tips/dns.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/troubleshooting/other-troubleshooting-tips/dns.md index 0c9205d18cd..0b877613274 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/troubleshooting/other-troubleshooting-tips/dns.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/troubleshooting/other-troubleshooting-tips/dns.md @@ -6,7 +6,7 @@ title: DNS 请确保你配置了正确的 kubeconfig（例如，为 Rancher HA 配置了 `export KUBECONFIG=$PWD/kube_config_cluster.yml`）或通过 UI 使用了嵌入式 kubectl。 -在运行 DNS 检查之前，请检查集群的默认 DNS 提供商，并确保[覆盖网络正常运行](networking.md#检查覆盖网络是否正常运行)，因为这也可能导致 DNS 解析（部分）失败。 +Before running the DNS checks, make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) for your DNS provider as this can also be the reason why DNS resolution (partly) fails. ## 检查 DNS pod 是否正在运行 diff --git a/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/dns.md b/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/dns.md index 9b3dcde419d..b2d8301e22d 100644 --- a/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/dns.md +++ b/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/dns.md @@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check name resolution issu Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml` for Rancher HA) or are using the embedded kubectl via the UI. -Before running the DNS checks, check the default DNS provider for your cluster and make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) as this can also be the reason why DNS resolution (partly) fails. +Before running the DNS checks, make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) for your DNS provider as this can also be the reason why DNS resolution (partly) fails. ## Check if DNS pods are running diff --git a/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/dns.md b/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/dns.md index 9b3dcde419d..b2d8301e22d 100644 --- a/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/dns.md +++ b/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/dns.md @@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check name resolution issu Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml` for Rancher HA) or are using the embedded kubectl via the UI. -Before running the DNS checks, check the default DNS provider for your cluster and make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) as this can also be the reason why DNS resolution (partly) fails. +Before running the DNS checks, make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) for your DNS provider as this can also be the reason why DNS resolution (partly) fails. ## Check if DNS pods are running diff --git a/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/dns.md b/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/dns.md index 9b3dcde419d..b2d8301e22d 100644 --- a/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/dns.md +++ b/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/dns.md @@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check name resolution issu Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml` for Rancher HA) or are using the embedded kubectl via the UI. -Before running the DNS checks, check the default DNS provider for your cluster and make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) as this can also be the reason why DNS resolution (partly) fails. +Before running the DNS checks, make sure that [the overlay network is functioning correctly](networking.md#check-if-overlay-network-is-functioning-correctly) for your DNS provider as this can also be the reason why DNS resolution (partly) fails. ## Check if DNS pods are running