• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1444
  • Last Modified:

remote desktop services server external DNS and FQDN

Greetings,

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 rds.domain.com to DNS and pointed it to the public IP of the RDS server. When I go to rds.domain.com, 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 remote.domain.com, 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.
0
king daddy
Asked:
king daddy
  • 6
  • 4
1 Solution
 
king daddyAuthor Commented:
so, don't know what's up but now it works. I wanted to verify all methods of connecting and entering rds.domain.com in an RDP client worked and I successfully connected.

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

thanks
0
 
king daddyAuthor Commented:
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.
0
 
king daddyAuthor Commented:
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 rds.domain.com and couldn't connect with an RDP client or IE. changed back to remoteBR.domain.local and now rds.domain.com is not working through an RDP client.

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

thx
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
smckeown777Commented:
As I mentioned on your other post, IE will always take you to port 80 - so unless you are running a website on the server this is normal(i.e. a blank page)

At end of the day we are looking at a DNS resolution issue I think

Pinging rds.domain.com(where domain.com I assume is your public domain name) doesn't return the correct ip no? If not then what does it return? Possibly just dns resolution hasn't propogated across the internet yet

Since you can RDP to it by IP then your firewall rules etc should all be good
0
 
king daddyAuthor Commented:
thanks.

domain.com 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.
0
 
smckeown777Commented:
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...
0
 
smckeown777Commented:
The other possibility is they(the DNS guys) didn't create the host name correctly - i.e. they didn't create a host called rds...host not found will be the result if so
0
 
king daddyAuthor Commented:
to clarify that statement, I went to a DNS website, entered rds.domain.com 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.

whatsmydns.net

just ran again and one in france and one in turkey report they can find it. none in the US
0
 
smckeown777Commented:
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
0
 
king daddyAuthor Commented:
INTERNAL! Glad you thought of it
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now