Tim: >> The /etc/nsswitch.conf file suggests otherwise, it's far from clear: >> >> # Example - obey only what nisplus tells us... >> #services: nisplus [NOTFOUND=return] files >> #networks: nisplus [NOTFOUND=return] files >> #protocols: nisplus [NOTFOUND=return] files >> #rpc: nisplus [NOTFOUND=return] files >> #ethers: nisplus [NOTFOUND=return] files >> #netmasks: nisplus [NOTFOUND=return] files >> >> The "obey only" suggests files will not be consulted. The behaviour of >> Joe's computer seems to indicate that kind of thing, too. >> >> Looking in the nsswitch.conf man file, I see: >> >> The ACTION value can be one of: >> >> return Return a result now. Do not call any further lookup Sam Varshavchik: > It's not the "return", but "NOTFOUND" that's the key. The status values are > described separately, elsewhere. > > An mdns resolver should return either NOTFOUND or SUCCESS for .local > lookups, and UNAVAIL for all other lookups. I'd be very hard pressed to reach that conclusion reading the information in the file or the man page. It's far from coherently written, and this seems counter to your explanation: # The entry '[NOTFOUND=return]' means that the search for an # entry should stop if the search in the previous entry turned # up nothing. Note that if the search failed due to some other reason # (like no NIS server responding) then the search continues with the # next entry. With your further explanation the less-than-obvious reason for "mdns4_minimal [NOTFOUND=return]" being here in the nsswitch.conf file: hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname is to stop DNS lookups of "something.local" kinds of names. Although the DNS resolver, itself, could be coded not to do that, and probably *should* be (since those addresses cannot ever be answered externally, and are a huge amount nuisance traffic on the internet). However, various people have found that it also puts the kybosh on normal DNS look-ups. Joe being just one. Though I wonder if his case was just the network restart was enough to kick things back into action, rather than editing the nsswitch.conf file? -- uname -rsvp Linux 3.10.0-1160.80.1.el7.x86_64 #1 SMP Tue Nov 8 15:48:59 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
