On Monday, August 31, 2020 1:39:37 PM MST Michael Catanzaro wrote:
On Mon, Aug 31, 2020 at 10:19 pm, Andreas Tunek andreas.tunek@gmail.com wrote:
I can't get that command to do anything useful in either F32 or F33.
You should see something like:
$ resolvectl query example.com example.com: 2606:2800:220:1:248:1893:25c8:1946 -- link: tun0 93.184.216.34 -- link: tun0
-- Information acquired via protocol DNS in 86.4ms. -- Data is authenticated: no
And that should be working out-of-the-box in F33.
However, if I write "http://nas-name.local in F32 in either Firefox or Gnome Web I can connect to my NAS, but if I write the same in F33 in the same programs I get an error.
Ah, I bet this your NAS is mDNS, which is broken right now: https://bugzilla.redhat.com/show_bug.cgi?id=1867830
Until the root cause is diagnosed, here is a workaround you can try. As root, open up /etc/authselect/user-nsswitch.conf and look at the hosts line. In a freshly-installed F33 system, it should look like this:
hosts: resolve [!UNAVAIL=return] myhostname files mdns4_minimal [NOTFOUND=return] dns
This says: "if resolved is running, and it doesn't return a hostname, then STOP and don't try anything else." Everything else is listed only for the case where resolved is not running. But since resolved is currently not resolving mDNS as expected, let's change it to check with avahi first, then check with resolved second, like this:
hosts: mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] myhostname files dns
Then, as root, run:
# authselect apply-changes
and then restart your browser. That's not the configuration we want to use in F33, but hopefully it will "fix" your problem. Please let me know if it works!
Michael
Michael,
The file is /etc/nsswitch.conf.