Same host, different domains, different ports, same IP address

Hi,

I have two applications running on a same server:

Application A
Application B

Server X with internal IP 10.0.0.10 and external 75.45.45.45 (simulated IPs)

Application A is accessed through port 8080
Application B is accessed through port 8081

GOAL:

I would like to access Application A through domain appA.com without having to put port number
I would like to access Application B through domain appB.com without having to put port number

What I have done so far:

- Pointed public DNS for both domains to the public IP
- Pointed private DNS for both domains to the internal IP
- Did a binding on IIS for both of them under same IP, differen domain and different port.

I am still unable to achieve what I would like to do.

QUESTIONS:

1) Is it possible to access these applications through their respective domains without having to enter port number?
2) What am I missing?

Thank you!!
ArgieITAsked:
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.

Cliff GaliherCommented:
If these are both web applications, you can only do what you want with a reverse proxy. You can't do it with DNS and IIS headers alone.
0
ArgieITAuthor Commented:
Hi Cliff, if that is the case, can you please expand on the reverse proxy solution? Thank you
0
Cliff GaliherCommented:
There are many reverse proxies out there. Apache can be one. Thin. Squid. Many UTMs have a reverse proxy option. But each ks very different in actual configuration. So I can't be more specific.

The general premise is the reverse proxy will listen on the public IP, on 80 and/or 443, look at the requested URL, make its own request to the end server on the ports you specify based on rules you create ahead of time, and then reply to the original request with the internal reply. So you can "hide" port changes and do advanced decision logic. But every implementation has their own way of writing those rules.
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
ArgieITAuthor Commented:
THanks Cliff; I guess I will have to investigate more on the reverse proxy as its still not very clear to me.

Would like to hear any other opinions if anybody is aware of any other ways to accomplish our goal.

Thank you
0
Pramod UbheCommented:
from dns prospective there is no option to hide port number however you can do the url re-dirction using reverse proxy.
if you can get help from your Linux admin he might know if that can be achievable in your environment.

in one of my prev. projects, we created a cname appA and pointed it to Linux server which had configuration to re-direct url with port number so users had to only type appA in their browser and it goes to the destination url with the port number.
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
Microsoft IIS Web Server

From novice to tech pro — start learning today.