What were you trying to do that didn't work?
When users customize their own RHEL images on top of existing images or running systems, the previous setting in'/etc/resolv.conf' might cause boot delay problem like RHEL-16394, rhbz#1545842 and rhbz#1862930.

It is recommended to cleanup '/etc/resolv.conf' to avoid it.

But not all know this tip and remember to cleanup it.

From the information we collected, RHEL images depend on NetworkManager to refresh '/etc/resolv.conf', it is too late for cloud-init while calling socket.getaddrinfo func.
Because other distribution images like Fedora, Amazon Linux, Ubuntu do not have this problem. I am suggesting we install systemd-resolved in all our clouds images and rhel guest image which do not need to cleanup '/etc/resolv.conf' anymore.

The steps are as below.

#yum install systemd-resolved
#systemctl enable --now systemd-resolved
#ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

Please provide the package NVR for which bug is seen:
5.14.0-427.13.1.el9_4.x86_64
How reproducible:
100%

Steps to reproduce

• start a RHEL-9.4 t3.small instance on aws
• update nameserver to another subnet in '/etc/resolv.conf'

Expected results
no boot delay 50s appears

Actual results
extra 50s took when nameserver is from other subnet like you boot your image in other subnet