anchor.diff:  If you do not create DHCP reservations, the installer requires reverse DNS resolution to set the hostnames for the Kubernetes API node, the provisioner node, the control plane nodes, and the worker nodes.
   ====
   
  -[discrete]
  +[id='network-requirements-ntp_{context}']
   == Network Time Protocol (NTP)
   
   Each {product-title} node in the cluster must have access to an NTP server. {product-title} nodes use NTP to synchronize their clocks. For example, cluster nodes use SSL certificates that require validation, which might fail if the date and time between the nodes are not in sync.
  
positive.code: 
  image::210_OpenShift_Baremetal_IPI_Deployment_updates_0122_2.png[Installer-provisioned networking]
  
  [discrete]
  == Configuring NICs
  
  {product-title} deploys with two networks:
  
negative.code: You can use the `dig` command to verify DNS resolution.
  ====
  
  [id='network-requirements-dhcp-reqs_{context}']
  == Dynamic Host Configuration Protocol (DHCP) requirements
  
  By default, installer-provisioned installation deploys `ironic-dnsmasq` with DHCP enabled for the `provisioning` network. No other DHCP servers should be running on the `provisioning` network when the `provisioningNetwork` configuration setting is set to `managed`, which is the default value. If you have a DHCP server running on the `provisioning` network, you must set the `provisioningNetwork` configuration setting to `unmanaged` in the `install-config.yaml` file.
  
  Network administrators must reserve IP addresses for each node in the {product-title} cluster for the `baremetal` network on an external DHCP server.
  
  [id='network-requirements-reserving-ip-addresses_{context}']
  == Reserving IP addresses for nodes with the DHCP server
  
  For the `baremetal` network, a network administrator must reserve a number of IP addresses, including:
  