Skip to content

Commit b09ec9c

Browse files
stevsmitstevsmit
authored
Merge pull request #96788 from dfitzmau/OCPBUGS-59795
OCPBUGS#59795: Reorg the troubleshooting disconnected docs
2 parents 4032933 + 95a435a commit b09ec9c

4 files changed

+69
-60
lines changed

‎modules/k8s-nmstate-troubleshooting-dns-disconnected-bind9-dns.adoc‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc
4+
5+
:_mod-docs-content-type: PROCEDURE
6+
[id="k8s-nmstate-troubleshooting-dns-disconnected-bind9-dns_{context}"]
7+
= Configuring the bind9 DNS named server
8+
9+
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.
10+
11+
.Procedure
12+
13+
. Add the `root-servers.net` zone at the end of the `/etc/named.conf` configuration file by running the following command:
14+
+
15+
[source,terminal]
16+
----
17+
$ cat >> /etc/named.conf <<EOF
18+
zone "root-servers.net" IN {
19+
type master;
20+
file "named.localhost";
21+
};
22+
EOF
23+
----
24+
25+
. Restart the `named` service by running the following command:
26+
+
27+
[source,terminal]
28+
----
29+
$ systemctl restart named
30+
----
31+
32+
. Confirm that the `root-servers.net` zone is present by running the following command:
33+
+
34+
[source,terminal]
35+
----
36+
$ journalctl -u named|grep root-servers.net
37+
----
38+
+
39+
.Example output
40+
[source,terminal]
41+
----
42+
Jul 03 15:16:26 rhel-8-10 bash[xxxx]: zone root-servers.net/IN: loaded serial 0
43+
Jul 03 15:16:26 rhel-8-10 named[xxxx]: zone root-servers.net/IN: loaded serial 0
44+
----
45+
46+
. Verify that the DNS server can resolve the NS record for the `root-servers.net` domain by running the following command:
47+
+
48+
[source,terminal]
49+
----
50+
$ host -t NS root-servers.net. 127.0.0.1
51+
----
52+
+
53+
.Example output
54+
+
55+
[source,terminal]
56+
----
57+
Using domain server:
58+
Name: 127.0.0.1
59+
Address: 127.0.0.53
60+
Aliases:
61+
root-servers.net name server root-servers.net.
62+
----
63+

‎modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc‎

Lines changed: 0 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -12,60 +12,3 @@ If you experience health check probe issues when configuring `nmstate` in a disc
1212
====
1313
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.
1414
====
15-
16-
== Configuring the bind9 DNS named server
17-
18-
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.
19-
20-
.Procedure
21-
22-
. Add the `root-servers.net` zone at the end of the `/etc/named.conf` configuration file by running the following command:
23-
+
24-
[source,terminal]
25-
----
26-
$ cat >> /etc/named.conf <<EOF
27-
zone "root-servers.net" IN {
28-
type master;
29-
file "named.localhost";
30-
};
31-
EOF
32-
----
33-
34-
. Restart the `named` service by running the following command:
35-
+
36-
[source,terminal]
37-
----
38-
$ systemctl restart named
39-
----
40-
41-
. Confirm that the `root-servers.net` zone is present by running the following command:
42-
+
43-
[source,terminal]
44-
----
45-
$ journalctl -u named|grep root-servers.net
46-
----
47-
+
48-
.Example output
49-
[source,terminal]
50-
----
51-
Jul 03 15:16:26 rhel-8-10 bash[xxxx]: zone root-servers.net/IN: loaded serial 0
52-
Jul 03 15:16:26 rhel-8-10 named[xxxx]: zone root-servers.net/IN: loaded serial 0
53-
----
54-
55-
. Verify that the DNS server can resolve the NS record for the `root-servers.net` domain by running the following command:
56-
+
57-
[source,terminal]
58-
----
59-
$ host -t NS root-servers.net. 127.0.0.1
60-
----
61-
+
62-
.Example output
63-
+
64-
[source,terminal]
65-
----
66-
Using domain server:
67-
Name: 127.0.0.1
68-
Address: 127.0.0.53
69-
Aliases:
70-
root-servers.net name server root-servers.net.
71-
----

‎modules/nw-understanding-networking-service-to-pod.adoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Key concepts of service-to-pod communication include:
2828

2929
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`.
3030

31-
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.
31+
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.
3232

3333
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:
3434

‎networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,10 @@ include::modules/virt-troubleshooting-incorrect-policy-config.adoc[leveloffset=+
2121
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc[leveloffset=+1]
2222

2323
// Creating a custom DNS host name to resolve DNS connectivity issues
24-
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc[leveloffset=+2]
24+
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-bind9-dns.adoc[leveloffset=+2]
2525

2626
// Configuring the dnsmasq DNS server
27-
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-dnsmasq.adoc[leveloffset=+2]
27+
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-dnsmasq.adoc[leveloffset=+2]
28+
29+
// Creating a custom DNS host name to resolve DNS connectivity issues
30+
include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc[leveloffset=+2]

0 commit comments

Comments
 (0)