OSDOCS-16614: Documented VIP optional with user-managed LB feature

Author: dfitzmau

modules/nw-dns-forward.adoc

@@ -20,9 +20,11 @@ endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * Provide a list of upstream DNS servers (`spec.upstreamResolvers`).
 * Change the default forwarding policy.
 
-[NOTE]
-====
 A DNS forwarding configuration for the default domain can have both the default servers specified in the `/etc/resolv.conf` file and the upstream DNS servers.
+
+[IMPORTANT]
+====
+During pod creation, Kubernetes uses the `/etc/resolv.conf` file that exists on a node. If you modify the `/etc/resolv.conf` file on a host node, the changes do not propagate to the `/etc/resolv.conf` file that exists in a container. You must recreate the container for changes to take effect.
 ====
 
 .Procedure

modules/virt-example-nmstate-IP-management.adoc

@@ -139,6 +139,11 @@ The following example shows a default situation that stores DNS values globally:
 
 * Configure a static DNS without a network interface. Note that when updating the `/etc/resolv.conf` file on a host node, you do not need to specify an interface, IPv4 or IPv6, in the `NodeNetworkConfigurationPolicy` (NNCP) manifest.
 +
+[IMPORTANT]
+====
+During pod creation, Kubernetes uses the `/etc/resolv.conf` file that exists on a node. If you modify the `/etc/resolv.conf` file on a host node, the changes do not propagate to the `/etc/resolv.conf` file that exists in a container. You must recreate the container for changes to take effect.
+====
++
 Example of a DNS configuration for a network interface that globally stores DNS values:
 +
 [source,yaml]