[Bug network/34515] New: resolver applies search path for AAAA queries even though ndots is exceeded
fabian--- via Glibc-bugs <[email protected]>
| Newsgroups | gmane.comp.lib.glibc.bugs |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://sourceware.org/bugzilla/show_bug.cgi?id=34515
Bug ID: 34515
Summary: resolver applies search path for AAAA queries even
though ndots is exceeded
Product: glibc
Version: 2.43
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: network
Assignee: unassigned at sourceware dot org
Reporter: [email protected]
Target Milestone: ---
With the following resolv.conf:
search suse.de
# implicit default: options ndots:1
Running "getent hosts code.qt.io" returns the IPv6 address for
"code.qt.io.suse.de":
> getent hosts code.qt.io
2a07:de40:b205:1c:10:144:53:65 gitlab.prg2.suse.org code.qt.io.suse.de
gitlab.suse.de
even though code.qt.io. exists:
> getent hosts code.qt.io.
54.247.17.180 code.qt.io
That is because the ndots option only attempts to do an AAAA lookup, which
fails:
> host -t AAAA code.qt.io
code.qt.io has no AAAA record
> host -t A code.qt.io
code.qt.io has address 54.247.17.180
That triggers the fallback to iterate the search list.
For consistency, the initial query for ndots should probably always attempt A
if AAAA is requested?
--
You are receiving this mail because:
You are on the CC list for the bug.