[SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

ArchyLife · 2025-11-24 01:02:47

Hi,

When I installed arch I used archinstall and for the Networking I left it on; Copy ISO Network configuration to installation

I did a Desktop install with i3 and I'm using the NetworkManager.

In the log it's giving me this message that I wanted to know if this message is ok for a home workstation using the NetworkManager, I also use wireguard/vpn.

NetworkManager[703]: <warn> [1763942688.9490] dns-sd-resolved[0d64a3849c95eec6]: send-updates SetLinkDomains@2 failed: GDBus.Error:org.freedesktop.resolve1.LinkBusy: Link enp6s0 is managed.

Here's the status for systemd-resolved.service and systemd-networkd

systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-11-23 14:04:40 UTC; 50min ago
Invocation: db7dff0061bd4dd7ae784e76c07d0230
TriggeredBy: ● systemd-resolved-monitor.socket
● systemd-resolved-varlink.socket
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://systemd.io/WRITING_NETWORK_CONF … N_MANAGERS
https://systemd.io/WRITING_RESOLVER_CLIENTS
Main PID: 497 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 38168)
Memory: 8.8M (peak: 13.3M)
CPU: 2.909s
CGroup: /system.slice/systemd-resolved.service
└─497 /usr/lib/systemd/systemd-resolved

systemctl status systemd-networkd
● systemd-networkd.service - Network Configuration
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-11-23 14:04:40 UTC; 52min ago
Invocation: 0d2e55f8a15843e0a8b7b8471db17a0b
TriggeredBy: ● systemd-networkd.socket
● systemd-networkd-varlink.socket
Docs: man:systemd-networkd.service(8)
man:org.freedesktop.network1(5)
Main PID: 496 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 38168)
FD Store: 0 (limit: 512)
Memory: 4M (peak: 16.8M)
CPU: 86ms
CGroup: /system.slice/systemd-networkd.service
└─496 /usr/lib/systemd/systemd-networkd

Also in /etc/resolv.conf it only shows the nameserver entry, as an example;(ip isn't real)

nameserver 100.12.1.1

I thought resolv.conf should also have these?

options edns0 trust-ad
search .

Any help would be greatly appreciated!

THANKS

Last edited by ArchyLife (2025-12-21 06:26:20)

system72 · 2025-11-24 01:55:17

having systemd-networkd enabled is unnecessary and can cause issues with networkmanager

https://wiki.archlinux.org/title/WireGuard#Usage
https://wiki.archlinux.org/title/WireGu … resolution

Last edited by system72 (2025-11-24 01:56:57)

ArchyLife · 2025-11-24 04:16:35

system72 wrote:

having systemd-networkd enabled is unnecessary and can cause issues with networkmanager
https://wiki.archlinux.org/title/WireGuard#Usage
https://wiki.archlinux.org/title/WireGu … resolution

Ahhh maybe systemd-networkd was enabled by default since I picked Copy ISO Network configuration to installation in archinstall, I didn't enable it myself by default.

Ok I disabled it and now the message is gone...

In /etc/NetworkManager/conf.d/ I created dns.conf with this entry;

[main]
dns=systemd-resolved

And now in /etc/resolv.conf it shows;

nameserver 100.0.0.0
options edns0
options trust-ad

I'm not sure what I am suppose to be seeing/looking at in the URLs you posted?

THANKS

-thc · 2025-11-24 06:21:44

systemd-resolved doesn't change your "/etc/resolv.conf" - it just works in "foreign" mode instead - you can check it via

resolvectl status

It should be running in "stub" mode which you can configure via

ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

ArchyLife · 2025-11-24 08:32:35

I've never used stub mode before in Linux, but it's my understanding it's recommended.

I meant before when I added in /etc/NetworkManager/conf.d/dns.conf with this entry;

[main]
dns=systemd-resolved

Then in /etc/resolv.conf it added these two;

options edns0
options trust-ad

Before it would only show nameserver

resolvectl status shows;

Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: foreign
  Current DNS Server: 100.0.0.0
         DNS Servers: 100.0.0.0
Fallback DNS Servers: 9.9.9.9#dns.quad9.net 2620:fe::9#dns.quad9.net 1.1.1.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google 2001:4860:4860::8888#dns.google

Link 2 (enp6s0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
         Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
       DNS Servers: 192.168.1.1
     Default Route: yes

Link 3 (wg0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
     Default Route: no

THANKS

Last edited by ArchyLife (2025-11-24 08:45:47)

ArchyLife · 2025-11-24 08:39:28

Here I changed it now to stub;

resolvectl status
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
Fallback DNS Servers: 9.9.9.9#dns.quad9.net 2620:fe::9#dns.quad9.net 1.1.1.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google 2001:4860:4860::8888#dns.google

Link 2 (enp6s0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
         Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
       DNS Servers: 192.168.1.1
     Default Route: yes

Link 3 (wg0)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 100.0.0.0
       DNS Servers: 100.0.0.0
        DNS Domain: ~.
     Default Route: yes

But can we see changes in /etc/resolv.conf, or we don't now? Now it's just the symlinked file from /run/systemd/resolve/stub-resolv.conf that you only see.

THANKS

Last edited by ArchyLife (2025-11-24 08:41:19)

-thc · 2025-11-24 09:23:43

systemd-resolved in stub mode has a static "/etc/resolv.conf" by design.
Changes due to VPN or other connections are changed in memory and are visible in "resolvectl".

Be aware that you seem to use WireGuard with "wg-quick" ("wg0" with default routing through WireGuard) which uses "resolveconf" to update DNS servers and is not really compatible with this (NetworkManager/system-resolved) configuration.

You should create a WireGuard connection in NetworkManager instead.

Last edited by -thc (2025-11-24 09:25:26)

ArchyLife · 2025-11-24 09:52:24

Ok so with using stub need to now use resolvectl status since /etc/resolv.conf will be static.

I edited some of the output in regards to Link 3 when I posted it by mistake.. Link 3 actually shows like this;

Link 3 (wg0-mullvad)

I'm not using WireGuard with "wg-quick" I'm actually using the mullvad-vpn app;

https://aur.archlinux.org/packages/mullvad-vpn

Here I ran resolvectl status again...

resolvectl status
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
Fallback DNS Servers: 9.9.9.9#dns.quad9.net 2620:fe::9#dns.quad9.net 1.1.1.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google 2001:4860:4860::8888#dns.google

Link 2 (enp6s0)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
         Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
       DNS Servers: 192.168.1.1
     Default Route: yes

Link 4 (wg0-mullvad)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 100.0.0.0
       DNS Servers: 100.0.0.0
        DNS Domain: ~.
     Default Route: yes

By the way, now for the wireguard, why does it show as Link 4 not Link 3?

THANKS

Last edited by ArchyLife (2025-11-24 10:00:14)

-thc · 2025-11-24 11:03:51

That's possibly a quirk of NetworkManager - every time a VPN disconnects and reconnects the number is incremented.

ArchyLife · 2025-11-24 21:50:03

-thc wrote:

That's possibly a quirk of NetworkManager - every time a VPN disconnects and reconnects the number is incremented.

Ok, thanks a lot @system72 and @-thc, I greatly appreciate the help...

Be well!

Last edited by ArchyLife (2025-11-24 21:50:21)

ArchyLife · 2025-12-17 07:35:41

I was looking back over this and forgot, before I added in /etc/NetworkManager/conf.d/dns.conf with this entry;

[main]
dns=systemd-resolved

But if I;m using "stub" mode;

ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

Should I keep dns=systemd-resolved in /etc/NetworkManager/conf.d/dns.conf ?

THANKS

Last edited by ArchyLife (2025-12-17 07:36:06)

-thc · 2025-12-17 07:51:54

From a strictly minimalist viewpoint: No. NetworkManager "realizes" on it's own that systemd-resolved is active and uses it. Nevertheless I keep the setting (for clarity).

ArchyLife · 2025-12-18 00:23:10

LOL, ok I'll keep the setting for Clarity...

THANKS

Last edited by ArchyLife (2025-12-18 00:23:26)

Arch Linux

#1 2025-11-24 01:02:47

[SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#2 2025-11-24 01:55:17

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#3 2025-11-24 04:16:35

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#4 2025-11-24 06:21:44

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#5 2025-11-24 08:32:35

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#6 2025-11-24 08:39:28

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#7 2025-11-24 09:23:43

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#8 2025-11-24 09:52:24

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#9 2025-11-24 11:03:51

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#10 2025-11-24 21:50:03

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#11 2025-12-17 07:35:41

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#12 2025-12-17 07:51:54

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

#13 2025-12-18 00:23:10

Re: [SOLVED] NM dns-sd-resolved send-updates SetLinkDomains@2 failed

Board footer