From f1d5dd2b58723b6816329463ba2782411c108659 Mon Sep 17 00:00:00 2001 From: dfitzmau Date: Tue, 3 Feb 2026 09:18:08 +0000 Subject: [PATCH] OSDOCS-16614-re: Implemented feedback on previous PR --- modules/installation-bare-metal-dns-record-type.adoc | 6 +++--- modules/nw-dns-forward.adoc | 2 +- modules/virt-example-nmstate-IP-management.adoc | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/modules/installation-bare-metal-dns-record-type.adoc b/modules/installation-bare-metal-dns-record-type.adoc index 4f46747963c6..44ec13db2c6a 100644 --- a/modules/installation-bare-metal-dns-record-type.adoc +++ b/modules/installation-bare-metal-dns-record-type.adoc @@ -4,7 +4,7 @@ // * installing/installing_bare_metal/upi/installing-bare-metal.adoc // * installing/installing_bare_metal/upi/installing-restricted-networks-bare-metal.adoc -:_mod-docs-content-type: CONCEPT +:_mod-docs-content-type: PROCEDURE [id="installation-bare-metal-dns-record-type_{context}"] = Configuring the dnsRecordsType parameter @@ -21,13 +21,13 @@ The `dnsRecordsType` parameter supports the following values: .Prerequisites -* You created DNS records, such as `api`, `api-int`, or `\*.apps`. +* You created DNS records, such as `api`, `api-int`, or `*.apps`. * You configured a user-managed load balancer for your cluster. * If you intend on setting `dnsRecordsType.External` in the `infrastructure.config.openshift.io` CR , you must initially configure cluster nodes to use the specific external server for DNS resolution. .Procedure -* During cluster installation, specify `TechPreviewNoUpgrade` for the `featureSet` parameter and specify `External` for the `dnsRecordsType` parameter in the `install-config.yaml` file: +* In the `install-config.yaml` file during cluster installation, specify `TechPreviewNoUpgrade` for the `featureSet` parameter and specify `External` for the `dnsRecordsType` parameter: + [source,yaml] ---- diff --git a/modules/nw-dns-forward.adoc b/modules/nw-dns-forward.adoc index e5d695499a2b..36b0ae6af165 100644 --- a/modules/nw-dns-forward.adoc +++ b/modules/nw-dns-forward.adoc @@ -24,7 +24,7 @@ A DNS forwarding configuration for the default domain can have both the default [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. +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 re-create the container for changes to take effect. ==== .Procedure diff --git a/modules/virt-example-nmstate-IP-management.adoc b/modules/virt-example-nmstate-IP-management.adoc index 2a02b16af2dd..d761cb9c3b86 100644 --- a/modules/virt-example-nmstate-IP-management.adoc +++ b/modules/virt-example-nmstate-IP-management.adoc @@ -141,7 +141,7 @@ The following example shows a default situation that stores DNS values globally: + [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. +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 re-create the container for changes to take effect. ==== + Example of a DNS configuration for a network interface that globally stores DNS values: