Why do the nodes get hostnames like dhcp-xxxx from DHCPv4 instead of pre-defined ones in DNS records during installation of RHOCP?

Issue

• Installing Red Hat OpenShift Container Platform and the nodes get the DHCP IP address along with the hostnames like dhcp-xxxx instead of the ones from the DNS records.

Jun 10 23:17:47 localhost kernel: vmxnet3 0000:0b:00.0 ens192: intr type 3, mode 0, 5 vectors allocated
Jun 10 23:17:47 localhost kernel: vmxnet3 0000:0b:00.0 ens192: NIC Link is Up 10000 Mbps
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0431] device (ens192): carrier: link connected
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0470] ovsdb: Could not connect: No such file or directory
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0485] device (ens192): state change: unavailable -> disconnected (reason 'none', sy>
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0516] policy: auto-activating connection 'Wired connection 1' (xxxxxxxx-85c5-3a1e-a>
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0522] device (ens192): Activation: starting connection 'Wired connection 1' (xxx>
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0523] device (ens192): state change: disconnected -> prepare (reason 'none', sys-if>
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0530] manager: NetworkManager state is now CONNECTING
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0532] device (ens192): state change: prepare -> config (reason 'none', sys-iface-st>
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0543] device (ens192): state change: config -> ip-config (reason 'none', sys-iface->
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0546] dhcp4 (ens192): activation: beginning transaction (timeout in 45 seconds)
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0674] dhcp4 (ens192): state changed unknown -> bound
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0688] device (ens192): state change: ip-config -> ip-check (reason 'none', sys-ifac>
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0702] device (ens192): state change: ip-check -> secondaries (reason 'none', sys-if>
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0704] device (ens192): state change: secondaries -> activated (reason 'none', sys-i>
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0710] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0723] manager: NetworkManager state is now CONNECTED_SITE
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0724] policy: set 'Wired connection 1' (ens192) as default for IPv4 routing and DNS
Jun 10 23:17:47 localhost NetworkManager[2692]: <info>  [1591831067.0725] policy: set-hostname: set hostname to 'dhcp-192-168-0-66' (from DHCPv4)
Jun 10 23:17:47 localhost dbus-daemon[2691]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolv>
Jun 10 23:17:47 dhcp-192-168-0-66 dbus-daemon[2691]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbu>
Jun 10 23:17:47 dhcp-192-168-0-66 systemd-hostnamed[2723]: Changed host name to 'dhcp-192-168-0-66'
Jun 10 23:17:47 dhcp-192-168-0-66 systemd-logind[2751]: New seat seat0.
Jun 10 23:17:47 dhcp-192-168-0-66 NetworkManager[2692]: <info>  [1591831067.0753] device (ens192): Activation: successful, device activated.
Jun 10 23:17:47 dhcp-192-168-0-66 NetworkManager[2692]: <info>  [1591831067.0758] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 10 23:17:47 dhcp-192-168-0-66 NetworkManager[2692]: <info>  [1591831067.0762] manager: startup complete
Jun 10 23:17:47 dhcp-192-168-0-66 systemd[1]: Started Network Manager Wait Online.
Jun 10 23:17:47 dhcp-192-168-0-66 systemd[1]: Reached target Network is Online.

• Why don't nodes getting a DHCP generated hostnames instead of the ones in DNS records?