Internet domain connecting to local servers?

Microsoft Windows server 2003 enterprise
July 26, 2010 at 18:51:16
Specs: Windows Server 2003
Hey everyone, couldn't fit a good subject line in. I have my own domain, let's say mycompany.com, and then my own Windows Server 2003 box that runs our Microsoft CRM server. Right now, if a user goes to crm.mycompany.com, it points it to our static IP so they can connect to CRM over the Internet. I just have a question about that though.

Is there any way to set it so that if a user is physically in the office, going to crm.mycompany.com will instead go to 10.0.0.50 which is our IP for the server? Right now they actually go to http://10.0.0.50 but it would be nice to have a domain address which is easier to remember. Problem is going to crm.mycompany.com sends the request over the Internet, which doesn't work since it's trying to connect to itself.

The reason I ask as well is because we're using Asterisk as our IP PBX on site and I want users to connect to the user portal to change their follow me settings and so on. When in the office or at home, I want them to be able to go to say asterisk.mycompany.com to make thoes changes. I don't want them to have to remember to go to one IP address while in the office, and then another when away from the office. Is that possible at all? Thanks!!!!


See More: Internet domain connecting to local servers?

Report •

#1
August 13, 2010 at 00:12:32
Hi edokid,

I'm by no means an expert on this subject matter, but I do have some experience at doing what you're proposing.

I've done the same thing with our company. I created an entry on our DNS that points to the IP I want to direct my Users to. This works for you while connected locally. For example, while outside the company on the Internet you could type "www.edokid.com" and be directed to your website. Locally, on your Intranet, you can set up an A Record on your DNS that will point to that same service locally and call it the same thing, "www.edokid.com". Since DNS is checked before reaching to the Internet for resolution, your local Users will be directed to the local source found on the DNS A Record.


Report •
Related Solutions


Ask Question