This error commonly appears on Ubuntu 22. The Defguard client uses resolvconf internally to configure DNS servers on the system. The only tested and supported backend is systemd-resolved.
Before proceeding, verify that systemd-resolved is running:
systemctl status systemd-resolvedOn Ubuntu 23 and later, resolvconf is a symbolic link to resolvectl by default. On Ubuntu 22 this link does not exist. The straightforward fix is to create it manually:
sudo ln -s /usr/bin/resolvectl /usr/sbin/resolvconfIf that fails, you can also try installing a package that provides the resolvconf command, such as openresolv. Note that using openresolv alongside systemd-resolved has not been tested and may cause conflicts — proceed with caution.
If DNS servers are configured in the location but users cannot resolve internal hostnames, check the following:
Routing — confirm requests to the network segments where your DNS servers reside are routed through the WireGuard interface:
ip routeWireGuard allowed IPs — confirm the DNS server network segments appear in the allowed ips list for the peer:
sudo wgManual resolution test — try resolving a name directly through one of your internal DNS servers:
dig @DNS_SERVER_IP my.internal.service.comLast updated
Was this helpful?
Was this helpful?