diff --git a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc
index f42ea8361c13..aa1e1f797591 100644
--- a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc
+++ b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc
@@ -11,7 +11,6 @@ You can install the Kubernetes NMState Operator by using the OpenShift CLI (`oc)
 .Prerequisites
 
 * You have installed the OpenShift CLI (`oc`).
-
 * You are logged in as a user with `cluster-admin` privileges.
 
 .Procedure
@@ -46,6 +45,7 @@ spec:
   - openshift-nmstate
 EOF
 ----
+
 . Subscribe to the `nmstate` Operator:
 +
 [source,terminal]
@@ -85,7 +85,38 @@ metadata:
 EOF
 ----
 
-. Verify that all pods for the NMState Operator are in a `Running` state by entering the following command:
+. 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
+----
++
+.. Monitor the `nmstate` CRD until the resource reaches the `Available` condition by running the following command. Ensure that you set a value for the `--timeout` option so that if the `Available` condition is not met within this set maximum waiting time, the command times out and generates an error message.
++
+[source,yaml]
+----
+$ oc wait --for=condition=Available nmstate/nmstate --timeout=600s
+----
+
+.Verification
+
+. Verify that all pods for the NMState Operator have the `Running` status by entering the following command:
 +
 [source,terminal]
 ----