Solved

DNS Hosts and IIS

Posted on 2013-11-07
3
170 Views
Last Modified: 2014-03-19
Dear All...
I have many local webapplication that are hosted in different servers and accesses with webpage contating the server name:

http://Server1name.domain/app1
http://Server2name.domain/app2

For security reasons i would like to consolidate all these webapplications to main webpage

http://main.domain/app1 to access the app1
http://main.domain/app2 to access the app2

you can just use the above url directly or go to the main page and click on App1 or App2 links.

What i am succedded to do is to creat the http://main.domain page (without using the server name) , i used Host (A) in DNS and adjusted the IIS but for the rest i dont know how to do them.

Kindlu advice.
0
Comment
Question by:mostabdo
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 15

Accepted Solution

by:
Giovanni Heward earned 500 total points
ID: 39630140
Options include moving each website folder structure to the central consolidated server, create symbolic links on the central server which point to the original servers, or use iframe tags (e.g. http://main.domain/app1 loads http://Server1name.domain/app1 via iframe, etc.)

mklink /d app1 \\Server1name.domain\x$\path\to\app1
mklink /d app2 \\Server2name.domain\x$\path\to\app2

Open in new window


http://www.w3schools.com/tags/tag_iframe.asp
0
 
LVL 15

Assisted Solution

by:Giovanni Heward
Giovanni Heward earned 500 total points
ID: 39630183
BTW, if you do copy folder structures centrally, or create a symbolic links, you'll need to globally modify the code to point to the new URI for any absolute links.  If coded to use relative links than you're in luck.  It's possible to have the legacy site run side by side with the new until completely tested.  Would recommend iframe first to avoid issues above, or redirect as a second choice, although iframe or redirect wouldn't necessarily address the "security reasons" you're eluding to, in which case you're left with manually migrating.

http://main.domain/app1
<iframe src="http://Server1name.domain/app1"></iframe>

http://main.domain/app2
<iframe src="http://Server2name.domain/app2"></iframe>
0
 

Author Comment

by:mostabdo
ID: 39630283
Thanks i will study these options and till you if it works
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I've written instructions for one router type, but this principle may be useful for others of the same brand and even other brands of router. Problem: I had an issue especially with mobile devices that refused to use DNS information supplied via…
Resolve DNS query failed errors for Exchange
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question