> On 1 May 2025, at 07:23, Mike Wright <nob...@nospam.hostisimo.com> wrote:
>
> (fqdn).
>
> How utilities such as as nslookup and dig figure out what to do when the
> final dot on a fqdn is missing is a mystery to me. Perhaps they always add a
> dot then trim the name to have no more than one. IDK
The lack of a trailing "." means that a failed lookup can be tried by adding
each term in the "search" list in /etc/resolve.conf.
My /etc/resolve.conf is:
$ cat /etc/resolv.conf
search internal
nameserver 172.17.1.1
And resolvectl reports:
$ resolvectl
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (enp0s5)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS
DNSSEC=no/unsupported
Current DNS Server: 172.17.1.1
DNS Servers: 172.17.1.1
DNS Domain: internal
Default Route: yes
Which means that "internal" will be added to any failed lookup.
This is a function of the algorithm in glibc and other libraries.
dig does not use the "search" list. You must provide FQDN to it.
nslookup will add suffixes from "search" list if the trailing "." is missing.
I prefer using "dig" because it you need to be explicit what you want queried.
(I think nslookup is deprecated with dig as the replacement)
Barry
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
