Repository: openshift/openshift-docs
Pull request #91520: OSDOCS-12848: Added /etc/resolv.conf modification to resolve DNS conn…
Author: login: dfitzmau
Labels: name: peer-review-done
description: Signifies that the peer review team has reviewed this PR
name: lgtm
description: Indicates that a PR is ready to be merged.
name: size/M
description: Denotes a PR that changes 30-99 lines, ignoring generated files.
name: jira/valid-reference
description: Indicates that this PR references a valid Jira ticket of any type.
name: branch/enterprise-4.19
Created: 2025-04-02T15:14:44Z | Merged: 2025-05-29T08:11:34Z

Version(s):
4.19

Issue:
[OSDOCS-12848](https://issues.redhat.com/browse/OSDOCS-12848)

Link to docs preview:
* [Creating a custom DNS host name to resolve DNS connectivity issues](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.html#k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc_k8s-nmstate-troubleshooting-node-network)
* [Installing the Kubernetes NMState Operator by using the CLI](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/networking_operators/k8s-nmstate-about-the-k8s-nmstate-operator.html#installing-the-kubernetes-nmstate-operator-CLI_k8s-nmstate-operator)


- [x] SME has approved this change (Mat K).
- [x] QE has approved this change (Ross.B).




Diff:
diff --git a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc
index f4a1d771a942..fb0e9db4cf2e 100644
--- a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc
+++ b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc
@@ -92,6 +92,30 @@ metadata:
 EOF
 ----
 
+. If your cluster has problems with the DNS health check probe because of DNS connectivity issues, you can add the following DNS host name configuration to the `NMState` CRD to build in health checks that can resolve these issues:
++
+[source,terminal]
+----
+apiVersion: nmstate.io/v1
+kind: NMState
+metadata:
+  name: nmstate
+spec:
+  probeConfiguration:
+    dns:
+      host: redhat.com
+# ...
+----
++
+.. Apply the DNS host name configuration to your cluster network by running the following command. Ensure that you replace `<filename>` with the name of your CRD file.
++
+[source,yaml]
+----
+$ oc apply -f <filename>.yaml
+----
+
+.Verification
+
 . Verify that all pods for the NMState Operator are in a `Running` state:
 +
 [source,terminal]
diff --git a/modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc b/modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
new file mode 100644
index 000000000000..33e89e019a27
--- /dev/null
+++ b/modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
@@ -0,0 +1,37 @@
+// 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-env-resolv.adoc_{context}"]
+= Creating a custom DNS host name to resolve DNS connectivity issues
+
+In a disconnected environment where the external DNS server cannot be reached, you can resolve Kubernetes NMState Operator health probe issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD). 
+
+.Procedure
+
+. Add the DNS host name configuration to the `NMState` CRD of your cluster:
++
+[source,yaml]
+----
+apiVersion: nmstate.io/v1
+kind: NMState
+metadata:
+  name: nmstate
+spec:
+  probeConfiguration:
+    dns:
+      host: redhat.com
+# ...
+----
+
+. Apply the DNS host name configuration to your cluster network by running the following command. Ensure that you replace `<filename>` with the name of your CRD file.
++
+[source,yaml]
+----
+$ oc apply -f <filename>.yaml
+----
+
+
+
+
diff --git a/modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc b/modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc
index 59101a1b8c75..f3c6cc2a7481 100644
--- a/modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc
+++ b/modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc
@@ -6,7 +6,7 @@
 [id="troubleshooting-dns-disconnected-env_{context}"]
 = Troubleshooting DNS connectivity issues in a disconnected environment
 
-If you experience DNS connectivity issues when configuring `nmstate` in a disconnected environment, you can configure the DNS server to resolve the list of name servers for the domain `root-servers.net`.
+If you experience health check probe issues when configuring `nmstate` in a disconnected environment, you can configure the DNS server to resolve the custom domain name instead of the default `root-servers.net` domain.
 
 [IMPORTANT]
 ====
@@ -15,8 +15,7 @@ Ensure that the DNS server includes a name server (NS) entry for the `root-serve
 
 == 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 NS record.
-For example you can use the `/var/named/named.localhost` as a zone file that already matches this criteria.
+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
 
@@ -69,4 +68,4 @@ Name: 127.0.0.1
 Address: 127.0.0.53
 Aliases:
 root-servers.net name server root-servers.net.
-----
\ No newline at end of file
+----
diff --git a/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc b/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc
index f063c995cc60..aa7d0dc6ec60 100644
--- a/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc
+++ b/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc
@@ -14,8 +14,14 @@ This includes issues such as:
 * The host loses connection to the default gateway.
 * The host loses connection to the API server.
 
+// Troubleshooting an incorrect node network configuration policy configuration
 include::modules/virt-troubleshooting-incorrect-policy-config.adoc[leveloffset=+1]
 
+// Troubleshooting DNS connectivity issues in a disconnected environment
 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]
+
+// Configuring the dnsmasq DNS server
 include::modules/k8s-nmstate-troubleshooting-dns-disconnected-env-dnsmasq.adoc[leveloffset=+2]
\ No newline at end of file


Reviews:
user: login: ocpdocs-vale-bot
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-03T13:48:20Z
user: login: mkowalski
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-29T14:11:52Z
user: login: mkowalski
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-29T14:13:36Z
user: login: mkowalski
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-29T14:16:11Z
user: login: dfitzmau
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-29T15:36:18Z
user: login: dfitzmau
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-29T15:38:37Z
user: login: michaelryanpeter
body: Nits, a question about applying the CRD to the cluster, and an out-of-scope concern re: eventual DITA migration.

/label peer-review-done
/remove-label peer-review-in-progress
/remove-label peer-review-needed
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-02T19:16:16Z
user: login: mkowalski
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T08:01:37Z
user: login: mkowalski
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T08:02:24Z
user: login: michaelryanpeter
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T13:25:53Z
user: login: dfitzmau
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-06T10:52:01Z
user: login: dfitzmau
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-06T10:54:49Z
user: login: dfitzmau
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-06T10:58:51Z

Review comments:
diff_hunk: @@ -92,6 +92,23 @@ metadata:
 EOF
 ----
 
+. Optional: In the event that your cluster enters a disconnected environment becuase of DNS connectivity issues, you can add the following DNS hostname configuration to the `NMState` CRD to build in health checks that can resolve these issues:
path: modules/k8s-nmstate-deploying-nmstate-CLI.adoc
user: login: ocpdocs-vale-bot
body: 🤖 **[error] RedHat.TermsErrors**: Use 'in case', 'if', or 'when' rather than 'In the event'. For more information, see [RedHat.TermsErrors](https://redhat-documentation.github.io/vale-at-red-hat/docs/main/reference-guide/termserrors).
created_at: 2025-04-03T13:48:20Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,27 @@
+// 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-env-resolv.adoc_{context}"]
+= Creating a custom DNS host name to resolve DNS connectivity issues
+
+In a disconnected environment where a host server cannot be reached, you can resolve DNS connectivity issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD). The Kubernetes NMState Operator adds the custom DNS host name to the `/etc/resolv.conf` file. If your cluster gets disconnected, the Operator reads the `/etc/resolv.conf` and uses the custom DNS host name to resolve the DNS connectivity issue.
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
user: login: mkowalski
body: I would write

>In a disconnected environment where **external DNS server** cannot be reached, you can resolve **operator health probe issues** by specifying a custom DNS host name in the `NMState` custom resource definition (CRD).

The remaining of the sentence, let's skip it because it's not correct -- I mean, it does not describe the feature we implemented


created_at: 2025-04-29T14:11:52Z
author_association: CONTRIBUTOR
diff_hunk: @@ -6,7 +6,7 @@
 [id="troubleshooting-dns-disconnected-env_{context}"]
 = Troubleshooting DNS connectivity issues in a disconnected environment
 
-If you experience DNS connectivity issues when configuring `nmstate` in a disconnected environment, you can configure the DNS server to resolve the list of name servers for the domain `root-servers.net`.
+If you experience DNS connectivity issues when configuring `nmstate` in a disconnected environment, you can configure the DNS server to resolve the list of name servers for the domain `root-servers.net`. Alternatively, you can resolve DNS connectivity issues by configuring a custom host name and then using the hostname to perform internal networking health checks on your cluster.
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc
user: login: mkowalski
body: Rather

>If you experience **health check probe issues** when configuring `nmstate` in a disconnected environment, you can configure the DNS server to resolve **the custom domain name instead of the default** domain `root-servers.net`.
created_at: 2025-04-29T14:13:36Z
author_association: CONTRIBUTOR
diff_hunk: @@ -92,6 +92,23 @@ metadata:
 EOF
 ----
 
+. Optional: If your cluster gets disconnected from a DNS server because of DNS connectivity issues, you can add the following DNS hostname configuration to the `NMState` CRD to build in health checks that can resolve these issues:
path: modules/k8s-nmstate-deploying-nmstate-CLI.adoc
user: login: mkowalski
body: Rather

>. Optional: If your cluster **has problems with DNS health check probe** because of DNS connectivity issues, you can add the following DNS hostname configuration to the `NMState` CRD to **customize the health check probe configuration**:
created_at: 2025-04-29T14:16:10Z
author_association: CONTRIBUTOR
diff_hunk: @@ -6,7 +6,7 @@
 [id="troubleshooting-dns-disconnected-env_{context}"]
 = Troubleshooting DNS connectivity issues in a disconnected environment
 
-If you experience DNS connectivity issues when configuring `nmstate` in a disconnected environment, you can configure the DNS server to resolve the list of name servers for the domain `root-servers.net`.
+If you experience DNS connectivity issues when configuring `nmstate` in a disconnected environment, you can configure the DNS server to resolve the list of name servers for the domain `root-servers.net`. Alternatively, you can resolve DNS connectivity issues by configuring a custom host name and then using the hostname to perform internal networking health checks on your cluster.
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc
user: login: dfitzmau
body: :heavy_check_mark: 
created_at: 2025-04-29T15:33:51Z
author_association: CONTRIBUTOR
diff_hunk: @@ -92,6 +92,23 @@ metadata:
 EOF
 ----
 
+. Optional: If your cluster gets disconnected from a DNS server because of DNS connectivity issues, you can add the following DNS hostname configuration to the `NMState` CRD to build in health checks that can resolve these issues:
path: modules/k8s-nmstate-deploying-nmstate-CLI.adoc
user: login: dfitzmau
body: :heavy_check_mark: 
created_at: 2025-04-29T15:36:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+// 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-env-resolv.adoc_{context}"]
+= Creating a custom DNS host name to resolve DNS connectivity issues
+
+In a disconnected environment where a host server cannot be reached, you can resolve DNS connectivity issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD). The Kubernetes NMState Operator adds the custom DNS host name to the `/etc/resolv.conf` file. If your cluster gets disconnected, the Operator reads the `/etc/resolv.conf` and uses the custom DNS host name to resolve the DNS connectivity issue.
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
user: login: dfitzmau
body: :+1: . I mentioned "Kubernetes NMState Operator" or do we want to be that specific?
created_at: 2025-04-29T15:38:37Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+// 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-env-resolv.adoc_{context}"]
+= Creating a custom DNS host name to resolve DNS connectivity issues
+
+In a disconnected environment where the external DNS server cannot be reached, you can resolve Kubernetes NMState Operator health probe issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD). 
+
+.Procedure
+
+* Add the DNS host name configuration to the `NMState` CRD of your cluster:
++
+[source,terminal]
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
user: login: michaelryanpeter
body: ```suggestion
[source,yaml]
```
created_at: 2025-05-02T18:55:22Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+// 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-env-resolv.adoc_{context}"]
+= Creating a custom DNS host name to resolve DNS connectivity issues
+
+In a disconnected environment where the external DNS server cannot be reached, you can resolve Kubernetes NMState Operator health probe issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD). 
+
+.Procedure
+
+* Add the DNS host name configuration to the `NMState` CRD of your cluster:
++
+[source,terminal]
+----
+apiVersion: nmstate.io/v1
+kind: NMState
+metadata:
+  name: nmstate
+spec:
+  probeConfiguration:
+    dns:
+      host: redhat.com
+# ...
+----
+
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
user: login: michaelryanpeter
body: Not to get out of scope and provide technical review, but would the customer need to run `oc create -f <filename>.yaml` or `oc apply -f <filename>.yaml`? I think that is how it usually works for CRDs.

If this change will be applied automatically, I think it would be a good idea to mention that.
created_at: 2025-05-02T19:01:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -15,8 +15,7 @@ Ensure that the DNS server includes a name server (NS) entry for the `root-serve
 
 == Configuring the bind9 DNS named server  
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc
user: login: michaelryanpeter
body: Out-of-scope, but addressing a concern: Procedures can only have one heading. Please keep in mind, once we migrate to DITA, block titles (ie `.Example`) won't work for items besides examples, tables, and features. https://docs.google.com/presentation/d/1yWZfJybc4SVxgXg4ZCmuBleuFpf8jSMEQkRar39mfdw/edit#slide=id.g304c4c806dd_0_53
created_at: 2025-05-02T19:08:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -92,6 +92,23 @@ metadata:
 EOF
 ----
 
+. Optional: If your cluster has problems with the DNS health check probe because of DNS connectivity issues, you can add the following DNS hostname configuration to the `NMState` CRD to build in health checks that can resolve these issues:
++
+[source,terminal]
+----
+apiVersion: nmstate.io/v1
+kind: NMState
+metadata:
+  name: nmstate
+spec:
+  probeConfiguration:
+    dns:
+      host: redhat.com
+# ...
+----
path: modules/k8s-nmstate-deploying-nmstate-CLI.adoc
user: login: michaelryanpeter
body: See the ISG guidance on [optional vs. conditional steps in procedures](https://www.ibm.com/docs/en/ibm-style?topic=format-procedures#indicating-optional-and-conditional-steps). This seems like a conditional step to me.

```suggestion
. If your cluster has problems with the DNS health check probe because of DNS connectivity issues, you can add the following DNS hostname configuration to the `NMState` CRD to build in health checks that can resolve these issues:
+
[source,yaml]
----
apiVersion: nmstate.io/v1
kind: NMState
metadata:
  name: nmstate
spec:
  probeConfiguration:
    dns:
      host: redhat.com
# ...
----
```
And not to give a technical review, but does this configuration file need to be created or applied by entering an `oc` command? 
created_at: 2025-05-02T19:11:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+// 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-env-resolv.adoc_{context}"]
+= Creating a custom DNS host name to resolve DNS connectivity issues
+
+In a disconnected environment where the external DNS server cannot be reached, you can resolve Kubernetes NMState Operator health probe issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD). 
+
+.Procedure
+
+* Add the DNS host name configuration to the `NMState` CRD of your cluster:
++
+[source,terminal]
+----
+apiVersion: nmstate.io/v1
+kind: NMState
+metadata:
+  name: nmstate
+spec:
+  probeConfiguration:
+    dns:
+      host: redhat.com
+# ...
+----
+
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
user: login: mkowalski
body: I am not sure what is meant by "this change will be applied automatically", but usually how we (in Engineering) see it is

1) you create a yaml file somewhere in your system, we don't care where, can be a file in your desktop
2) you run `oc apply -f path-to-the-file`
3) done

The issue with `oc create [...]` is that it does **not** allow to modify a resource that already exists. So it is desired to use `apply`, not `create`
created_at: 2025-05-05T08:01:36Z
author_association: CONTRIBUTOR
diff_hunk: @@ -92,6 +92,23 @@ metadata:
 EOF
 ----
 
+. Optional: If your cluster has problems with the DNS health check probe because of DNS connectivity issues, you can add the following DNS hostname configuration to the `NMState` CRD to build in health checks that can resolve these issues:
++
+[source,terminal]
+----
+apiVersion: nmstate.io/v1
+kind: NMState
+metadata:
+  name: nmstate
+spec:
+  probeConfiguration:
+    dns:
+      host: redhat.com
+# ...
+----
path: modules/k8s-nmstate-deploying-nmstate-CLI.adoc
user: login: mkowalski
body: `oc apply -f ...` is needed for this change to be effective
created_at: 2025-05-05T08:02:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+// 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-env-resolv.adoc_{context}"]
+= Creating a custom DNS host name to resolve DNS connectivity issues
+
+In a disconnected environment where the external DNS server cannot be reached, you can resolve Kubernetes NMState Operator health probe issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD). 
+
+.Procedure
+
+* Add the DNS host name configuration to the `NMState` CRD of your cluster:
++
+[source,terminal]
+----
+apiVersion: nmstate.io/v1
+kind: NMState
+metadata:
+  name: nmstate
+spec:
+  probeConfiguration:
+    dns:
+      host: redhat.com
+# ...
+----
+
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
user: login: michaelryanpeter
body: Thank you for clarifying!
created_at: 2025-05-05T13:25:53Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,27 @@
+// 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-env-resolv.adoc_{context}"]
+= Creating a custom DNS host name to resolve DNS connectivity issues
+
+In a disconnected environment where the external DNS server cannot be reached, you can resolve Kubernetes NMState Operator health probe issues by specifying a custom DNS host name in the `NMState` custom resource definition (CRD). 
+
+.Procedure
+
+* Add the DNS host name configuration to the `NMState` CRD of your cluster:
++
+[source,terminal]
+----
+apiVersion: nmstate.io/v1
+kind: NMState
+metadata:
+  name: nmstate
+spec:
+  probeConfiguration:
+    dns:
+      host: redhat.com
+# ...
+----
+
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc
user: login: dfitzmau
body: Thanks. I added the additionally step about applying the configuration to the cluster network. Unless I should state to apply the configuration to nodes?


created_at: 2025-05-06T10:52:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -15,8 +15,7 @@ Ensure that the DNS server includes a name server (NS) entry for the `root-serve
 
 == Configuring the bind9 DNS named server  
path: modules/k8s-nmstate-troubleshooting-dns-disconnected-env.adoc
user: login: dfitzmau
body: Thanks. I'll leave the structure as is for now until the DITA migration path is clearer.
created_at: 2025-05-06T10:54:49Z
author_association: CONTRIBUTOR
diff_hunk: @@ -92,6 +92,23 @@ metadata:
 EOF
 ----
 
+. Optional: If your cluster has problems with the DNS health check probe because of DNS connectivity issues, you can add the following DNS hostname configuration to the `NMState` CRD to build in health checks that can resolve these issues:
++
+[source,terminal]
+----
+apiVersion: nmstate.io/v1
+kind: NMState
+metadata:
+  name: nmstate
+spec:
+  probeConfiguration:
+    dns:
+      host: redhat.com
+# ...
+----
path: modules/k8s-nmstate-deploying-nmstate-CLI.adoc
user: login: dfitzmau
body: Thanks. I added this step.
created_at: 2025-05-06T10:58:51Z
author_association: CONTRIBUTOR

PR comments:
user: login: openshift-ci-robot
created_at: 2025-04-02T15:14:56Z
body: @dfitzmau: This pull request references [OSDOCS-12848](https://issues.redhat.com//browse/OSDOCS-12848) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91520):

>…ect issues
>
><!--- PR title format: [GH#<gh-issue-id>][BZ#<bz-issue-id>][OCPBUGS#<jira-issue-id>][OSDOCS#<jira-issue-id>]: <short-description-of-the-pr> --->
>
><!--- If your changes apply to the latest release and/or in-development version of OpenShift, open your PR against the `main` branch.
>Do not create or rename a top-level directory (or any subdirectory in a directory that contains a hugebook.flag file) in the repository and topic map without checking with a docs program manager first.
>If a book is being created or modified, there are changes on the Customer Portal that must also be made.
>
>* For more details about the information requested in this template, see:
>  https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/create_or_edit_content.adoc#submit-PR --->
>
>Version(s):
><!--- Specify the version or versions of OpenShift your PR applies to. -->
>
>Issue:
><!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->
>
>Link to docs preview:
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>
>QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-04-02T15:15:28Z
body: @dfitzmau: This pull request references [OSDOCS-12848](https://issues.redhat.com//browse/OSDOCS-12848) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91520):

>Version(s):
>4.19
>
>Issue:
>[OSDOCS-12848](https://issues.redhat.com/browse/OSDOCS-12848)
>
>Link to docs preview:
>
>
>- [ ] SME has approved this change.
>- [ ] QE has approved this change.
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: ocpdocs-previewbot
created_at: 2025-04-02T15:20:48Z
body: 🤖 Tue May 06 11:11:44 - Prow CI generated the docs preview:

https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.html
https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/networking_operators/k8s-nmstate-about-the-k8s-nmstate-operator.html
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-04-03T13:54:06Z
body: @dfitzmau: This pull request references [OSDOCS-12848](https://issues.redhat.com//browse/OSDOCS-12848) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91520):

>Version(s):
>4.19
>
>Issue:
>[OSDOCS-12848](https://issues.redhat.com/browse/OSDOCS-12848)
>
>Link to docs preview:
>* [Creating a custom DNS host name to resolve DNS connectivity issues](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.html#k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc_k8s-nmstate-troubleshooting-node-network)
>
>
>- [ ] SME has approved this change.
>- [ ] QE has approved this change.
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-04-07T09:51:42Z
body: @dfitzmau: This pull request references [OSDOCS-12848](https://issues.redhat.com//browse/OSDOCS-12848) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91520):

>Version(s):
>4.19
>
>Issue:
>[OSDOCS-12848](https://issues.redhat.com/browse/OSDOCS-12848)
>
>Link to docs preview:
>* [Creating a custom DNS host name to resolve DNS connectivity issues](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.html#k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc_k8s-nmstate-troubleshooting-node-network)
>
>
>- [ ] SME has approved this change (Mat K).
>- [ ] QE has approved this change.
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: mkowalski
created_at: 2025-05-02T07:22:43Z
body: /lgtm
author_association: CONTRIBUTOR
user: login: openshift-ci-robot
created_at: 2025-05-02T10:50:38Z
body: @dfitzmau: This pull request references [OSDOCS-12848](https://issues.redhat.com//browse/OSDOCS-12848) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91520):

>Version(s):
>4.19
>
>Issue:
>[OSDOCS-12848](https://issues.redhat.com/browse/OSDOCS-12848)
>
>Link to docs preview:
>* [Creating a custom DNS host name to resolve DNS connectivity issues](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.html#k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc_k8s-nmstate-troubleshooting-node-network)
>
>
>- [x] SME has approved this change (Mat K).
>- [ ] QE has approved this change.
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-05-02T10:51:40Z
body: @dfitzmau: This pull request references [OSDOCS-12848](https://issues.redhat.com//browse/OSDOCS-12848) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91520):

>Version(s):
>4.19
>
>Issue:
>[OSDOCS-12848](https://issues.redhat.com/browse/OSDOCS-12848)
>
>Link to docs preview:
>* [Creating a custom DNS host name to resolve DNS connectivity issues](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.html#k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc_k8s-nmstate-troubleshooting-node-network)
>* [Installing the Kubernetes NMState Operator by using the CLI](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/networking_operators/k8s-nmstate-about-the-k8s-nmstate-operator.html#installing-the-kubernetes-nmstate-operator-CLI_k8s-nmstate-operator)
>
>
>- [x] SME has approved this change (Mat K).
>- [ ] QE has approved this change.
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: michaelryanpeter
created_at: 2025-05-02T18:48:10Z
body: /label peer-review-in-progress
author_association: CONTRIBUTOR
user: login: openshift-ci[bot]
created_at: 2025-05-06T11:13:16Z
body: @dfitzmau: all tests **passed!**


[Full PR test history](https://prow.ci.openshift.org/pr-history?org=openshift&repo=openshift-docs&pr=91520). [Your PR dashboard](https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:dfitzmau).

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
author_association: NONE
user: login: rbbratta
created_at: 2025-05-29T05:11:14Z
body: /lgtm
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-05-29T08:10:04Z
body: @dfitzmau: This pull request references [OSDOCS-12848](https://issues.redhat.com//browse/OSDOCS-12848) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91520):

>Version(s):
>4.19
>
>Issue:
>[OSDOCS-12848](https://issues.redhat.com/browse/OSDOCS-12848)
>
>Link to docs preview:
>* [Creating a custom DNS host name to resolve DNS connectivity issues](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.html#k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc_k8s-nmstate-troubleshooting-node-network)
>* [Installing the Kubernetes NMState Operator by using the CLI](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/networking_operators/k8s-nmstate-about-the-k8s-nmstate-operator.html#installing-the-kubernetes-nmstate-operator-CLI_k8s-nmstate-operator)
>
>
>- [x] SME has approved this change (Mat K).
>- [x] QE has approved this change.
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-05-29T08:10:13Z
body: @dfitzmau: This pull request references [OSDOCS-12848](https://issues.redhat.com//browse/OSDOCS-12848) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91520):

>Version(s):
>4.19
>
>Issue:
>[OSDOCS-12848](https://issues.redhat.com/browse/OSDOCS-12848)
>
>Link to docs preview:
>* [Creating a custom DNS host name to resolve DNS connectivity issues](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.html#k8s-nmstate-troubleshooting-dns-disconnected-env-resolv.adoc_k8s-nmstate-troubleshooting-node-network)
>* [Installing the Kubernetes NMState Operator by using the CLI](https://91520--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/networking_operators/k8s-nmstate-about-the-k8s-nmstate-operator.html#installing-the-kubernetes-nmstate-operator-CLI_k8s-nmstate-operator)
>
>
>- [x] SME has approved this change (Mat K).
>- [x] QE has approved this change (Ross.B).
>
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: dfitzmau
created_at: 2025-05-29T08:11:56Z
body: /cherrypick enterprise-4.19
author_association: CONTRIBUTOR
user: login: openshift-cherrypick-robot
created_at: 2025-05-29T08:12:43Z
body: @dfitzmau: new pull request created: #93893

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91520#issuecomment-2918658767):

>/cherrypick enterprise-4.19


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE