external rds with a .local address

[sted]

I have in the past got rds(/rdp) working in one of 2 ways the last one i did was a brand new from scratch domain so ive used a real world domain name (bought) and a real cert. Thats obviously the best way to do it. The other way was done years ago as a proof of concept and used a self signed cert and a altered hosts file to point external clients at the server.

 

So if i have an internal domain name of school.internal and an external domain of school.com how do i get the rds.school.com to resolve externally (and ideally internally) to the appropriate ip and how do i get the rds server whos's real name is rds.school.internal to take a cert for rds.school.com. I assume name resolution is the easy bit i just externally go to my name providers control panel and point rds.school.com to whatever external ip my rds server has and i can create an internal dns zonr for domain.com (as long as im not using it for an actual website) and create an a record pointing at the rds internal ip address. Its more the certificate im worried about as i assume a server called rds.school.local isnt going to be happy with a cert saying its rds.school.com

[LukeC]

Our rds system is set up on a .local domain. We have split DNS in place so when users request a external address they check our local DNS first. Before going out on the web. The cert only contains the external address as this is the only address being resolved hope it makes sense.

[Steve21]

There's a powershell command to change the external gateway addresses to something different e.g. the cert name so it doesn't become an issue

 

Set-RDSessionCollectionConfiguration –CollectionName QuickSessionCollection -CustomRdpProperty “use redirection server name:i:1 `n alternate full address:s:remote.domain.com” 

 

Obviously need to change the addresses Then makes it show to the external world as the certificate name (for us gateway.school.wilts.sch.uk, so our *.school.wilts.sch.uk cert works)

 

Steve