Request for remedial DNS help

[tregas]

I'm sure that this is pretty easy for most of you here, so I hope I can get this resolved soon. This is happening in a Windows domain using Microsoft's DNS server. Here's the breakdown...

I have a client who needed remote access to their terminal server. They had a domain name no longer being used, so I configured it as an easy name for access to their terminal server. That FQDN is:

https://remote.clientdomain.com

Easy enough and it works fine. Now, I need to configure that same FQDN to work on their LAN as they have an application which runs on the IIS on that same server. That FQDN works out to be:

https://remote.clientdomain.com/app

The problem is that the internal domain name for the client is:

clientname.local

So, here's the question. How do I configure internal DNS so that they can enter the FQDN's already working on the internet to work on their LAN? In other words, how can I set up an internal alias (CNAME) which has the correct domain that is different than the Windows domain?

Thanks!

---
Tyler Regas - Nerd. Writer.

 

[elgrandeperro]

forward that domain to your DNS server?

 

[tregas]

Could you please be more specific? I'm technically savvy, but not in DNS. My DNS skills are limited to very basic setup and configuration. Any hints you could give me would be appreciated.

Thanks!

---
Tyler Regas - Nerd. Writer.

 

[elgrandeperro]

Their "Lan" must have a DNS server. If you forward requests from that DNS server for the zone clientdomain.com to your DNS server (which is housing clientdomain.com), then it will appear for all intents and purposes as being
valid. I assume your created clientdomain.com as an authoritative zone on your DNS server?

http://technet.microsoft.com/en-us/library/cc739169(WS.10).aspx

So how it would work, when the lan users query for remote.clientdomain.com, their DNS will forward the request to yours (provided you have connectivity). You will supply the correct answers from your DNS server.

 

[tregas]

Gotcha. Thanks! I'm not sure what happened, but it appears to be working now. I added a domain within the local domain and added a (A) record which pointed to the correct machine. It was not working, so I removed it.

My colleague went in later and did the same thing, and then left it. Last night when we checked, it was working and resolving the correct address internally.

We're not sure why they wanted it, but they did. Its my preference to not perform work which doesn't yield any real benefit. If, however, they are happy to not make a bookmark and to type more characters than they have to on their LAN, then that's apparently up to them.

We bill them the same amount.

Thanks for the help and better understanding of DNS

---
Tyler Regas - Nerd. Writer.