+++ This bug was initially created as a clone of Bug #1984876 +++

Description of problem:
TRY in resolv.conf options:

options timeout:1
options attempts:1

OR 

options attempts:1  timeout:1


Version-Release number of selected component (if applicable):
bind-9.16.15-3.el9.x86_64

How reproducible:

always

Steps to Reproduce:
/etc/resolv.conf has an options, like:
options timeout:1
options attempts:1


RHEL8
# cat /etc/resolv.conf 
; Created by cloud-init on instance boot automatically, do not edit.
;
# Generated by NetworkManager
options timeout:1
options attempts:1
nameserver 1.2.3.4

# time dig localhost

; <<>> DiG 9.11.26-RedHat-9.11.26-4.el8_4 <<>> localhost
;; global options: +cmd
;; connection timed out; no servers could be reached

real	0m2.011s
user	0m0.006s
sys	0m0.004s

#### WITH options timeout:15 it takes 30s
=> options do something ....

RHEL9:

# time host localhost
;; connection timed out; no servers could be reached


real	0m10.009s
user	0m0.007s
sys	0m0.004s

=====> options timeout:1 or options timeout:30 DO NO CHANGE


Actual results:
options exists

Expected results:

works as expected

Additional info:

--- Additional comment from Petr Sklenar on 2021-07-22 13:41:43 CEST ---


ANOTHER ISSUE in resolv.conf (lazy to fill another bz)

write 'typos in ns'


 cat  /etc/resolv.conf
; Created by cloud-init on instance boot automatically, do not edit.
;
# Generated by NetworkManager
nameserver 1.2.3.4,1
nameserver 8.8.8.8
-----

RHEL8: line is ignored, so next one works!
rhel9: it ends:

# cat /etc/resolv.conf
; Created by cloud-init on instance boot automatically, do not edit.
;
# Generated by NetworkManager
nameserver 1.2.3.4,1
nameserver 8.8.8.8

# dig localhost
dig: parse of /etc/resolv.conf failed

--- Additional comment from Petr Menšík on 2021-08-04 14:46:05 CEST ---

I would not consider comment #1 as an issue. I think reporting obviously wrong resolv.conf with invalid entries should not be silently ignored, but reported to user.

If an address is in invalid format, just report it. Different issue would be for example with IPv6 link-local address, which at least for some time delv were unable to parse. Not sure it is still the case. But for invalid addresses, I think fatal error is okay.

--- Additional comment from Petr Menšík on 2021-08-04 14:58:49 CEST ---

Some changes are related to removed lwres library, which originally parsed /etc/resolv.conf. It were moved to irs library, which parses some parts different way.