WireGuard connection doesn't work when no DNS is provided

Hello Etfz,

Thank you for getting in touch with us. To better assist you, could you kindly provide us with the following information:

• Your current RDM version.

• The operating system you are using and its version.

• The data source you are utilizing.

• Any additional information and screenshots you believe might be relevant.

• A recording showing the steps that led to the issue? This will allow us to investigate and try to reproduce the issue. (I sent you a Direct message with the information to provide us with the recording.)

Once we have this information, we will be better equipped to diagnose and resolve the issue.

Best regards,

Hi,

• Remote Desktop Manager 2024.3.20
• Windows 10 22H2 (19045)
• SQL Server data source

Uploaded a recording.

Hello,

Thank you for the information!

I will try to reproduce the behaviour on my end and will let you know the result as soon as possible. In the meantime, could you please try to update your RDM to the latest version (2024.3.27.0) and see if the behaviour is the same?

Thank you for letting us know. If you have any other questions, feel free to let us know.

Best regards,

Hi,

The issue persists in 2024.3.27.0.

Hello,

Thank you for your response!

Unfortunately, I am unable to reproduce the behaviour. I sent all the information to our QA Team to see if they can reproduce your issue.

I will provide you with more information as soon as possible. In the meantime, if you have any other questions, feel free to let us know.

Best regards,

Hi,

Thank you. To be clear, you're saying that it does work for you even without entering any DNS server for the WireGuard configuration?

Hello,

Thank you for your response, and sorry for the delay!

Unfortunately, I wasn't able to replicate the environment to use WireGuard. I've shared all the information with our QA Team, and an infrastructure with WireGuard is currently in progress to be created so that we can test this on our end to see if we are able to reproduce your issue.

I will provide you with more information as soon as possible. In the meantime, if you have any other questions, feel free to let us know.

Best regards,

Hello etfz,

We've implemented a fix for this issue—when no DNS is provided, localhost will now be added automatically, and the field is now required. This should ensure that WireGuard connections work as expected.

The fix should be available in version 2025.1.20. Let us know if this resolves the issue for you!

Best regards,

Hello etfz,

We've implemented a fix for this issue—when no DNS is provided, localhost will now be added automatically, and the field is now required. This should ensure that WireGuard connections work as expected.

The fix should be available in version 2025.1.20. Let us know if this resolves the issue for you!

Best regards,

@David Godin


I actually have the opposite problem now because of the requirement.

My issue is that if I am connected to WG from at the office I only want to route a specific DOMAIN over the WG network (split tunneling), I am able to do this with a MSRPT rule on Windows and it worked fine, in that my work domain lookups would happen to my local DC and my home network would traverse based on AllowedIPs.

The issue now is DNS is required and if I plug in either DNS server (Home or Work) the other side that is not part of that network will fail resolving.

Hello @corey01,

Thank you for the detailed explanation.
We’ve created an internal ticket to properly address this scenario and review the behavior around the DNS requirement and split tunneling use cases. We’ll keep you informed of the progress here as we move forward.

Regards,