Issue Description:
Usually after specifying a DNS when creating a Remote Access Gateway, the DNS will be specified in extClient/RAC configuration. While the extClient/RAC is running, the domain name will be looked up with the specified DNS server.
There is one issue reported on Ubuntu 24.04, the specified DNS server does not take effect. The root cause is not identified. It should be caused by some changes between Ubuntu 22.04(No issue) and Ubuntu 24.04.
There are similar issues in community,
Workaround 1:
There is no permanent solution yet, the workaround is to edit the DNS configuration file manually, and then to add the customized DNS server at the first place. /etc/resolv.conf or /etc/systemd/resolved.conf, it depends on resolv.conf or systemd-resolved used on the system. For systemd-resolved, after the change, please run systemctl restart systemd-resolved to restart the service.
With this workaround, it's not necessary to specify the DNS server in extClient/RAC configuration file, because it's already setup in OS level.
Workaround 2:
If the customized DNS server is the CoreDNS installed together with Netmaker, and there is netclient installed on the server side(so that the nm server owns a VPN ip in the netmaker network), the alternative is to specify the coredns' vpn ip, rather than its public ip, for example,
[Interface]
Address = 10.10.255.254/32,fdb8:9c9c:c340:df22:ffff:ffff:ffff:fffe/128
PrivateKey = XXXXXXXXXXX
MTU = 1420
DNS = 10.10.0.12 ->rather than the public ip
Specify this IP on your Remote Access Gateway's DNS field so that new RAC connections and newly created VPN config files can pick it up.
It works with the vpn ip on Ubuntu 24.04. This way, it does not need to update the DNS setup in OS level.