openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #98187 from openshift-cherrypick-robot/cherry-pick-96788-to-enterprise-4.20

Browse Source 
[enterprise-4.20] OCPBUGS#59795: Reorg the troubleshooting disconnected docs
This commit is contained in:
Steven Smith
2025-08-28 13:18:19 -04:00
committed by GitHub
parent 4d29bfcb11 ba9083372d
commit a5d8eef1e2
4 changed files with 69 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files

63
modules/k8s-nmstate-troubleshooting-dns-disconnected-bind9-dns.adoc Normal file
View File

@@ -0,0 +1,63 @@
// Module included in the following assemblies:
//
// * networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc
:_mod-docs-content-type: PROCEDURE
[id="k8s-nmstate-troubleshooting-dns-disconnected-bind9-dns_{context}"]
= Configuring the bind9 DNS named server
For a cluster configured to query a `bind9` DNS server, you can add the `root-servers.net` zone to a configuration file that contains at least one DNS record. For example you can use the `/var/named/named.localhost` as a zone file that already matches this criteria.
.Procedure
. Add the `root-servers.net` zone at the end of the `/etc/named.conf` configuration file by running the following command:
+
[source,terminal]
----
$ cat >> /etc/named.conf <<EOF
zone "root-servers.net" IN {
type master;
file "named.localhost";
};
EOF
----
. Restart the `named` service by running the following command:
+
[source,terminal]
----
$ systemctl restart named
----
. Confirm that the `root-servers.net` zone is present by running the following command:
+
[source,terminal]
----
$ journalctl -u named|grep root-servers.net
----
+
.Example output
[source,terminal]
----
Jul 03 15:16:26 rhel-8-10 bash[xxxx]: zone root-servers.net/IN: loaded serial 0
Jul 03 15:16:26 rhel-8-10 named[xxxx]: zone root-servers.net/IN: loaded serial 0
----
. Verify that the DNS server can resolve the NS record for the `root-servers.net` domain by running the following command:
+
[source,terminal]
----
$ host -t NS root-servers.net. 127.0.0.1
----
+
.Example output
+
[source,terminal]
----
Using domain server:
Name: 127.0.0.1
Address: 127.0.0.53
Aliases:
root-servers.net name server root-servers.net.
----

57
modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc
View File

@@ -12,60 +12,3 @@ If you experience health check probe issues when configuring `nmstate` in a disc
====
Ensure that the DNS server includes a name server (NS) entry for the `root-servers.net` zone. The DNS server does not need to forward a query to an upstream resolver, but the server must return a correct answer for the NS query.
====
== Configuring the bind9 DNS named server
For a cluster configured to query a `bind9` DNS server, you can add the `root-servers.net` zone to a configuration file that contains at least one DNS record. For example you can use the `/var/named/named.localhost` as a zone file that already matches this criteria.
.Procedure
. Add the `root-servers.net` zone at the end of the `/etc/named.conf` configuration file by running the following command:
+
[source,terminal]
----
$ cat >> /etc/named.conf <<EOF
zone "root-servers.net" IN {
type master;
file "named.localhost";
};
EOF
----
. Restart the `named` service by running the following command:
+
[source,terminal]
----
$ systemctl restart named
----
. Confirm that the `root-servers.net` zone is present by running the following command:
+
[source,terminal]
----
$ journalctl -u named|grep root-servers.net
----
+
.Example output
[source,terminal]
----
Jul 03 15:16:26 rhel-8-10 bash[xxxx]: zone root-servers.net/IN: loaded serial 0
Jul 03 15:16:26 rhel-8-10 named[xxxx]: zone root-servers.net/IN: loaded serial 0
----
. Verify that the DNS server can resolve the NS record for the `root-servers.net` domain by running the following command:
+
[source,terminal]
----
$ host -t NS root-servers.net. 127.0.0.1
----
+
.Example output
+
[source,terminal]
----
Using domain server:
Name: 127.0.0.1
Address: 127.0.0.53
Aliases:
root-servers.net name server root-servers.net.
----

2
modules/nw-understanding-networking-service-to-pod.adoc
View File

@@ -28,7 +28,7 @@ Key concepts of service-to-pod communication include:
Services use selectors to identify the pods that should receive the traffic. The selectors match labels on the pods to determine which pods are part of the service. Example: A service with the selector `app: myapp` will route traffic to all pods with the label `app: myapp`.
Endpoints are dynamically updated to reflect the current IP addresses of the pods that match the service selector. {product-name} maintains these endpoints and ensures that the service routes traffic to the correct pods.
Endpoints are dynamically updated to reflect the current IP addresses of the pods that match the service selector. {product-title} maintains these endpoints and ensures that the service routes traffic to the correct pods.
The communication flow refers to the sequence of steps and interactions that occur when a service in Kubernetes routes traffic to the appropriate pods. The typical communication flow for service-to-pod communication is as follows:

7
networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc
View File

@@ -21,7 +21,10 @@ include::modules/virt-troubleshooting-incorrect-policy-config.adoc[leveloffset=+
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc[leveloffset=+1]
// Creating a custom DNS host name to resolve DNS connectivity issues
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc[leveloffset=+2]
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-bind9-dns.adoc[leveloffset=+2]
// Configuring the dnsmasq DNS server
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-dnsmasq.adoc[leveloffset=+2]
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-dnsmasq.adoc[leveloffset=+2]
// Creating a custom DNS host name to resolve DNS connectivity issues
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc[leveloffset=+2]