netclient does not set a Connection-specific DNS suffix on Windows

[elieawad]

Netclient on windows adapter does not setup a connection-specific DNS suffix, when compared to wireguard, it sets it up if the network name (suffix) is set as DNS server over the netmake network.
is this a limitation of netmaker ce v0.90.0 ? if not, is there any plans to make it possible for netclient to set the suffix part of the join process?
This extremely useful for nodes on windows to resolve hostnames of other nodes ont he same netmaker vpn network using their local hostname.

Any help is much appreciated.

[VishalDalwadi]

Hi @elieawad, this is unfortunately a known issue. And we are working on it.

In the meantime, the workaround for setting connection-specific DNS suffixes on Windows requires setting NRPT rules.

Run the following command as admin in Powershell on all the nodes that you run netclient on.

Add-DnsClientNrptRule -Namespace "<network-domain-suffix>" -NameServers "<netclient-node-ip-addr>"

To remove the rule, run the following command.

Remove-DnsClientNrptRule -Namespace "<network-domain-suffix>"

The <network-domain-suffix> would be the same as network name. But please check the suffixes of the DNS records in the DNS tab in your network to be sure.

The <netclient-node-ip-addr> is the IP address of the node in the netmaker network.

[VishalDalwadi]

@elieawad with v1.0.0, we added support for SearchList. You can now reach your nodes with <hostname>.<network-name>.