Link to home
Create AccountLog in
Avatar of king daddy
king daddyFlag for United States of America

asked on

remote desktop services server external DNS and FQDN


I built a 2008 R2 server for RDS. I named it RemoteBR.domain.local. This was about 3 months ago. Just getting back to this, I had the company which manages our external DNS add to DNS and pointed it to the public IP of the RDS server. When I go to, I can't connect. I suspect I need to change the FQDN of the RDS server somewhere in the RDS settings, or somewhere else, or something. I am new to RDS and it's associated DNS settings, but our current terminal server on 2003 is named ts.domain.local and our current DNS is, and it works, so I'm not sure where to go from here.

To note, I can get to it internally by the FQDN and LAN IP address and externally by the public IP.

Thanks for any guidance.
Avatar of king daddy
king daddy
Flag of United States of America image


so, don't know what's up but now it works. I wanted to verify all methods of connecting and entering in an RDP client worked and I successfully connected.

However, when I enter the public IP or into Internet Explorer, it takes me to my firewall. That ain't good. Any ideas?

my IP block is .34 - .38. The WAN entry on my firewall is .34. Can I change that to .38 without issue?

thanks. just posting as I find stuff.
I changed to .38 and was still connected. got error on .34 and .38 brought me to the firewall in IE.

changed the rd session host server name to and couldn't connect with an RDP client or IE. changed back to remoteBR.domain.local and now is not working through an RDP client.

not sure how to set this up so the IP and, using IE, bring me to the remote server.

Avatar of Shane McKeown
Shane McKeown
Flag of Ireland image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
thanks. is my public domain name and pinging it does not return an IP address. it return host could not be found.

I agree it may be DNS, but weird that they said they did it awhile back and it still hasn't propagated. I saw that it was on only one DNS server tested, in Seattle. No where else in the world according to the map on the website I used to test it.

thanks again.
If they did this a while back then it will have propagated...
But to confirm all this you need to ping from EXTERNAL to your LAN just to be sure(and eliminate anything internal out of the loop)

'I saw that it was on only one DNS server tested, in Seattle' - what are you saying here? Not understanding this statement...
The other possibility is they(the DNS guys) didn't create the host name correctly - i.e. they didn't create a host called not found will be the result if so
to clarify that statement, I went to a DNS website, entered and it showed me a map of the world with several servers listed. All of them returned an error except for one server in Seattle.

just ran again and one in france and one in turkey report they can find it. none in the US
Oh...and that one in Seattle - it returns the correct ip?

That's very strange for sure...this record you say was setup over a month ago? I know DNS propagation is slow...but not that slow!!

Not sure what would cause that
INTERNAL! Glad you thought of it