Merge pull request #71379 from slovern/TELCODOCS-900

TELCODOCS-900 DHCP must be used for IPI installations

Author: stevsmit

installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc

@@ -29,6 +29,8 @@ include::modules/ipi-install-extracting-the-openshift-installer.adoc[leveloffset
 
 include::modules/ipi-install-creating-an-rhcos-images-cache.adoc[leveloffset=+1]
 
+include::modules/ipi-install-setting-cluster-node-hostnames-dhcp.adoc[leveloffset=+1]
+
 [id="ipi-install-configuration-files"]
 [id="additional-resources_config"]
 == Configuring the install-config.yaml file

modules/ipi-install-setting-cluster-node-hostnames-dhcp.adoc

@@ -0,0 +1,18 @@
+// Module included in the following assemblies:
+//
+//  *installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc
+
+:_mod-docs-content-type: CONCEPT
+[id="ipi-install-setting-cluster-node-hostnames-dhcp_{context}"]
+= Setting the cluster node hostnames through DHCP
+
+On {op-system-first} machines, hostnames are is set through `NetworkManager`. 
+By default, the machines obtain their hostnames through DHCP. 
+If hostnames are not provided by DHCP, set statically through kernel arguments, or another method, they are obtained through a reverse DNS lookup. 
+Reverse DNS lookup occurs after the network has been initialized on a node and can take time to resolve. 
+Other system services can start prior to this and detect hostnames as `localhost` or similar. 
+You can avoid this delay in assigning hostnames by using DHCP to provide the hostname for each cluster node.
+
+Additionally, setting the hostnames through DHCP can bypass any manual DNS record name configuration errors in environments that have a DNS split-horizon implementation.
+
+