RDM connections using RDG do not use RDG machine to resolve destination IP address
RDM connections using RDG do not use RDG machine to resolve destination IP address
In both the Mac and the Windows apps, if an internal DNS name is used as the destination session, the RD gateway machine resolves the DNS. The iOS app (apparently) does not resolve destination host names at the gateway, causing connection failures.
We run in AWS and use both a private domain (.aws) and public domain (.com) via Route 53.
Consider the following:
RD Gateway machine DNS name 'rdg.public.com' resolves to a public IP address
Destination machine public DNS 'destination.internal.ourdomain.com' resolves to a private IP address (10.0.0.0/16)
Destination machine private DNS 'destination.ourdomain.aws' resolves to the same private IP address as 'destination.internal.ourdomain.com'
A connection set up to use the RD gateway that specifies the destination publicly-accessible DNS entry with the non-routable address connects. But using the internal, private DNS entry (which resolves to the same address when queried at the RD gateway) fails.
Thanks.
All Comments (4)
Hi,
We're currently looking into your issue.
Best regards,
Mathieu Morrissette
Hi,
In your gateway settings, Is "Bypass RD Gateway server for local addresses" enabled? If so, can you try disabling it and tell us if it works or still doesn't.
Best regards
Mathieu Morrissette
No, it's not enabled because it would make no sense. None of the private addresses are "local" (to the client). They are only local to the Amazon VPC.
Hi,
We were unable to reproduce the issue on our environment. Would it be possible for you to provide us a test access to your current setup so we can try to find and resolve the issue? You can email me at : mmorrissette@devolutions.net
Best regards
Mathieu Morrissette