Hi,
At Each reboot from my fedora server 34 the same story occurs since a recent update
I m getting this :
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (enp5s0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 3 (bridge0)
Current Scopes: none
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Servers: 192.168.5.10 192.168.5.2
Failed to get link data for 4: Unknown object '/org/freedesktop/resolve1/link/_34'.
Failed to get link data for 5: Unknown object '/org/freedesktop/resolve1/link/_35'.
Failed to get link data for 6: Unknown object '/org/freedesktop/resolve1/link/_36'.
Failed to get link data for 7: Unknown object '/org/freedesktop/resolve1/link/_37'.
Failed to get link data for 8: Unknown object '/org/freedesktop/resolve1/link/_38'.
Failed to get link data for 9: Unknown object '/org/freedesktop/resolve1/link/_39'.
Failed to get link data for 10: Unknown object '/org/freedesktop/resolve1/link/_310'.
Failed to get link data for 11: Unknown object '/org/freedesktop/resolve1/link/_311'.
Failed to get link data for 12: Unknown object '/org/freedesktop/resolve1/link/_312'.
Failed to get link data for 13: Unknown object '/org/freedesktop/resolve1/link/_313'.
Failed to get link data for 14: Unknown object '/org/freedesktop/resolve1/link/_314'.
Failed to get link data for 15: Unknown object '/org/freedesktop/resolve1/link/_315'.
Failed to get link data for 16: Unknown object '/org/freedesktop/resolve1/link/_316'.
Failed to get link data for 17: Unknown object '/org/freedesktop/resolve1/link/_317'.
Failed to get link data for 18: Unknown object '/org/freedesktop/resolve1/link/_318'.
Failed to get link data for 19: Unknown object '/org/freedesktop/resolve1/link/_319'.
Failed to get link data for 20: Unknown object '/org/freedesktop/resolve1/link/_320'.
While I should get this:
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (enp5s0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 3 (bridge0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
DNS Servers: 192.168.5.10 192.168.5.2
Link 4 (virbr7)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 5 (virbr3)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 6 (virbr1)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 7 (virbr8)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 8 (virbr4)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 9 (virbr6)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 10 (virbr0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 11 (virbr2)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 12 (vnet0)
Current Scopes: LLMNR/IPv6
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 13 (vnet1)
Current Scopes: LLMNR/IPv6
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 14 (vnet2)
Current Scopes: LLMNR/IPv6
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 15 (vnet3)
Current Scopes: LLMNR/IPv6
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 16 (vnet4)
Current Scopes: LLMNR/IPv6
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 17 (vnet5)
Current Scopes: LLMNR/IPv6
Which is what I get when I m restarting the service but it’s still annoying.
Especially since I can’t set any global dns server since there is not /etc/resolvconf folder.
But anyway since the configuration didn’t change, it must be a wrong startup booting sequence for resolvectl