Out of my area of expertise, but reading the systemd-resolved man page (may not be the latest, but close enough) says that local apps get name resolution requests one of 3 ways:
**Entire text: The glibc getaddrinfo(3) API as defined by RFC3493[1] and its
related resolver functions, including gethostbyname(3). This
API is widely supported, including beyond the Linux platform.
In its current form it does not expose DNSSEC validation
status information however, and is synchronous only. This API
is backed by the glibc Name Service Switch (nss(5)). Usage of
the glibc NSS module nss-resolve(8) is required in order to
allow glibc's NSS resolver functions to resolve hostnames via
systemd-resolved.
- systemd-resolved via D-Bus OR a Linux socket (Ways 1 and 2)
- glibc getaddrinfo API** (Way 3)
**Entire text: The glibc getaddrinfo(3) API as defined by RFC3493[1] and its
related resolver functions, including gethostbyname(3). This
API is widely supported, including beyond the Linux platform.
In its current form it does not expose DNSSEC validation
status information however, and is synchronous only. This API
is backed by the glibc Name Service Switch (nss(5)). Usage of
the glibc NSS module nss-resolve(8) is required in order to
allow glibc's NSS resolver functions to resolve hostnames via
systemd-resolved.
Statistics: Posted by bls — Thu Oct 17, 2024 3:06 am