Adding alternative FQDN for local domain.

Question

Hi,
I'm trying to configure RDS for my standalone Windows Server 2012 Essentials and it's almost done.
(Probablly) last thing i need to do is to change FQDN for my local domain to .com to use RDS externaly.
So, like i said, i've done dyndns config, added ssl cert, configured RDWeb, RD Gateway, RD License and RD Broker.
Now, when i'm logging into remote.mydomain.com/RDWeb , i can login with Active Directory credentials, get rdp i try login into server. But i can only try, becuase there is an error about wrong FQDN for server (know and not new error for anyone). So, what I
had done was changing FQDN for my domain by this powershell script http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80 (if anyone had problems with digitally unsigned script, google for "Set-ExecutionPolicy Unrestricted"), in
theory, this script changed FQDN, but in reality, i still have same problem trying to connect externally.
I also read that i should add new DNS Zone for my .com domain and there add (A) record for my subdomain for remote desktop, that points to internal IP adress of my server. When i tried that, it was even worse because i couldn't even open RDWeb site. When that
dns zone was deleted, everything came back to previous state.
And now i'm here, out of ideas. Any suggestion what I did wrong? Maybe it was something with this DNS Zone for .com ? Maybe there should be Zone, but not normal one but "stub zone"?
I would be happy for any suggestion.

Answer 1

" suspect we may have a basic mis-understanding of what each of us is trying to say.  Let me try again. 
There are (at least) three ways to reach a LAN computer from the internet with Essentials.  Remote Web Access, direct RDP and VPN.  There are also third party solutions, such as Go To My PC and Log Me In.  The third party type
usually involve a subscription model with recurring charges, the others may involve a fee for SSL certificates, but they are (usually) much less expensive and do not rely on a third party."
Yes, i can agree we difinitelly had problem with mis-uderstanding so, sorry for that. I was talking about direct RDP to my server because Anywhere Access is already configured (but remote desktop from there to server opened only Essential Dashboard, that's
why i left this solution). Also, like i said, i'm aware of risks and i'll
take responsibility for that.
"Direct RDP is configured at the router and points the port (3389, but it can be changed) to the IP of the device you want to contact.  then, simply opening the RDP applet on your remote computer and typing in the public IP of the router/firewall
will automatically connect you to the chosen computer.  This is a very high security risk and should be avoided when ever possible."
Here is double facapalm for me - when you wrote about 3389 TCP port, i got enlightenment that i didn't do that (because i ealier tried to work on 443 with Anywhere Access and forgot about it), also information i got after tries to connect weren't usefull neither
- because Windows gave me back information about wrong FQDN, i was strictly focused on that problem, but like we know now, problem was in much different place. When i opened that port, everything started to be like i wanted (i also find out, after testing
RDP client from remoteapp in web menu that why i'm using this when i want to used direct RDP anyway). So much facepalm.
Next thing for now will be different port then 3389 and in future, VPN instead of direct RDP.
Anyway, really, thanks for help!