[Feature]: common DNS server & domain setting to work properly in Active Directory environments

[unquietwiki]

As it stands right now, Netmaker generates host file content for each member node, and propagates that across the network. Wireguard has an option for a DNS server setting, and a domain search setting; that would seem to be useful in an AD-enabled environment, wherein other member systems may not be on the network; plus end-user systems could be properly joined to an AD domain. This would be particularly useful in a professional deployment. Thanks.

[unquietwiki]

#2721 may also be asking for something like this.

[unquietwiki]

"Expanding the configuration" shows a working DNS command for the Wireguard config.

ArchLinux also has documentation for this setting in config files; look up "DNS ="

[unquietwiki]

Per discussion with @abhishek9686 on Discord, the remote client gateway feature already has a DNS host setting. Not sure if it works with adding domains as well; will need to test. It also sounded like SaaS will have some kind of CoreDNS addon feature per the 0.22.0 changes; not sure how my original request here ties in with that.

[unquietwiki]

Okay... so the client gateway works with an accepted DNS + suffix search string in the default config. The mesh clients don't have a setting for this; I understand it might conflict with Linux setups (plus you can set /etc/resolv.conf), but Windows setups could definitely use it.

In the meantime, I did identify PowerShell commands that could be scripted to set this on a periodic basis (particularly if the adapter gets recreated by "netclient pull").

Set-DnsClientServerAddress -InterfaceAlias netmaker -ServerAddresses ("2001:db8::1","192.0.2.1")
Set-DnsClient -InterfaceAlias netmaker -ConnectionSpecificSuffix example.com