You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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").
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.
The text was updated successfully, but these errors were encountered: