DNS Lookup issues with MacOS Tahow 26.2 and RDM 2025.3.9.2 - Cannot connect to RDP servers
DNS Lookup issues with MacOS Tahow 26.2 and RDM 2025.3.9.2 - Cannot connect to RDP servers
I do not know if it is the Tahoe 26.2 upgrade or the RDM 2025.3.9.2 update as they were both updated at the same time.
But with these update I can not longer connect to Microsoft Windows Server using RDP protocol.
From an Terminal in MacOS, I can successfully do DNS lookups on from a local DNS server (I.E server.domain.local). I can also ping by DNS name from MacOS Terminal.
I can also successfully connect to Microsoft Windows Servers using RDP with the Microsoft Windows App. This leads me to believe the issue is with RDM.
When I use RDM to connect to server, the error I get is: Unable to connect to "server.domain.local" - DNS_Name_Not-Found.
How do I roll back RDM version? Anyone else have this issue?
Is there a solution for RDM version 2025.3.9.2 for the DNS_Name_Not_Founmd error?
All Comments (2)
Hello,
Thank you for reaching out regarding this matter.
For the time being, I recommend rolling back to the previous version. To do so, please uninstall the current version and install an earlier one, which you can find in the Previous Versions section of the RDM download page on our website. Note that your local RDM configuration will not be deleted.
We will investigate this issue on our end and notify you once it is safe to update.
Thank you for your patience.
Best regards,
Jacob Lafrenière
Hi
Just to follow up on what Jacob wrote: we had a very similar issue logged recently, and it was resolved on the customer side by rebooting their machine. As much as I hate to suggest that as a solution, it would be worth trying. In that case is was clearly "something" in the OS DNS resolver that was misbehaving. If that was true in your case, I might also expect that rolling back RDM would not solve the issue. Regardless, I encourage you to stay with the updated version and try a reboot.
Internally, for RDP, it's using freerdp and DNS resolution is just a call to getaddrinfo. Nothing on our side has changed here in any recent version. It's likely the Windows App is using its own DNS resolver. I don't know what `ping` uses for DNS resolution. If you were to enable session logging in RDM and recreate the problem, the exact error code from getaddrinfo would be logged but it is not usually very helpful.
Please let me know if you have any questions
Kind regards,
Richard Markievicz