anchor.diff:  .Reserving IP addresses so they become static IP addresses
   ====
   Some administrators prefer to use static IP addresses so that each node's IP address remains constant in the absence of a DHCP server. To use static IP addresses in the {product-title} cluster, reserve the IP addresses with an infinite lease. During deployment, the installer will reconfigure the NICs from DHCP assigned addresses to static IP addresses. NICs with DHCP leases that are not infinite will remain configured to use DHCP.
  +====
  +
  +[IMPORTANT]
  +.Ensuring that your DHCP server can provide infinite leases
  +====
  +Your DHCP server must provide a DHCP expiration time of 4294967295 seconds to properly set an infinite lease as specified by link:https://datatracker.ietf.org/doc/html/rfc2131[rfc2131]. If a lesser value is returned for the DHCP infinite lease time, the node reports an error and a static IP is not set for the node. In RHEL 8, `dhcpd` does not provides infinite leases. If you want to use the provisioner node to serve dynamic IP addresses with infinite lease times, use `dnsmasq` rather than `dhcpd`.
   ====
   
   [IMPORTANT]
  
positive.code: When using a VLAN, each NIC must be on a separate VLAN corresponding to the appropriate network.
  ====
  
  [discrete]
  == DNS requirements
  
  Clients access the {product-title} cluster nodes over the `baremetal` network. A network administrator must configure a subdomain or subzone where the canonical name extension is the cluster name.
  
negative.code: 
  image::210_OpenShift_Baremetal_IPI_Deployment_updates_0122_2.png[Installer-provisioned networking]
  
  [id='network-requirements-config-nics_{context}']
  == Configuring NICs
  
  {product-title} deploys with two networks:
  