Dear community,
Please help me with fixing systemd-resolved after upgrading to 33. I am not using a VPN, I have just a simple home LAN network to which my laptop connects via WiFi (interface wlp4s0). There are virtual interfaces for my VMs, but I’m not sure if they are affecting anything here.
After upgrading to Fedora 33 I noticed that hostname resolution no longer works for my LAN machines. What’s weird is that it works one way: IP → hostname, but not hostname → IP:
> resolvectl domain
Global:
Link 2 (enp0s31f6):
Link 3 (wlp4s0): ~.
Link 4 (virbr0):
Link 5 (virbr0-nic):
> resolvectl dns
Global:
Link 2 (enp0s31f6):
Link 3 (wlp4s0): 192.168.1.1
Link 4 (virbr0):
Link 5 (virbr0-nic):
One of the LAN hosts is called “dkpi”, here I can see it:
> resolvectl query 192.168.1.115
192.168.1.115: dkpi -- link: wlp4s0
-- Information acquired via protocol DNS in 3.4ms.
-- Data is authenticated: no
But at the same time:
> resolvectl query dkpi
dkpi: resolve call failed: 'dkpi' not found
> nslookup dkpi
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find dkpi: SERVFAIL
There is nothing “fancy” in the network setup, just auto-DNS driven by the router.
One more output if it helps:
> resolvectl
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (enp0s31f6)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 3 (wlp4s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1
DNS Domain: ~.
Link 4 (virbr0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 5 (virbr0-nic)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Could please anyone give a hint what could be the issue? Thanks!