windows server 2012 R1, REMOTE DESKTOP CONNECTION

I have a domain.com that is  registered with siteground.com, the company bought a new server and asked me to configure as terminal server (remote desktop connection).this company is getting all internet connectivity through optimum.net, using their public IP, their DNS . this company is not hosting any DC or DNS servers.

 The server which i configured was already having domain.local.

I created A record in forward lookup zone. (remote.domain.local) and did forwarding to their public dns server.

now i need an A record created for this server to be on ISP DNS.

since this server has .local , can i create A record on ISP console, i think it won't work as only domain.com is registered
and.local is internal domain name.

so how should i map domain.local to domain.com so a valid A record can be created.both domain name is similar except that of .local and .com


should i create cname , if so where at ISP or at registrar, or is there any other way.

or can i create an internal A record under forward lookup zone as remote. domain. com on server domain.local and create A record for remote. domain.com and point to IP of domain.local on NAT.
pramod1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris DentPowerShell DeveloperCommented:
Create remote.domain.com and use the public IP then NAT back to the terminal server.

For this bit:

> or can i create an internal A record under forward lookup zone as remote. domain. com on server domain.local

Create a zone named remote.domain.com, add a Host (A) record with a blank name using the internal IP address of your terminal server.

Once done, whether they're inside or out, your clients will be able to use remote.domain.com to access the terminal server.

Chris
0
Aaron TomoskySD-WAN SimplifiedCommented:
If the environment is small, I really think you should consider moving off .local
I recommend doing a subdomain of the public name like local.domain.com. Other common subdomains are internal, I, corp, cityname, etc...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SteveCommented:
.local domains were intended to be internal only and should not be referred to externally. Most people avoid them altogether these days as it's not ideal to use them.

If moving your internal domain to a new domain isn't practical, amend your internet facing applications (eg exchange, IIS etc) to use the public FQDN (eg remote.domain.com) and just keep the .local address for internal use.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers

From novice to tech pro — start learning today.

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.