Note that there are some explanatory texts on larger screens.

plurals
  1. PONetwork Systems Help: How to route an external request, by hostname to an internal ip?
    primarykey
    data
    text
    <p>Welcome to my first question on stack overflow.</p> <p>I've looked around, and I haven't found this question asked yet. However, that may be because I don't know how to ask the question that I need answered.</p> <p><strong>THE INFORMATION:</strong></p> <p>I'm a programmer who left the public sector that had a, surprisingly, well-managed IT department that had all this crap working for me. I now work for a private company that needs a bit of network systems help.</p> <p>We have:</p> <ul> <li>A SQL Server</li> <li>An Application Server</li> <li>A File Server</li> <li>A Web Server <ul> <li>multiple web services</li> <li>team foundation server</li> <li>share point services</li> </ul></li> <li>5 desktops</li> </ul> <p>all on our internal network.</p> <p>We also have: - No domain controller - No Internal DNS / NAT / DHCP Server.</p> <p>We're currently using a router for DHCP and Port Forwarding. We are getting a static IP assigned today.</p> <p><strong>THE QUESTION:</strong></p> <p>What do I need to setup in order to point our external domains / subdomains to our new static IP and have those requests routed (by the hostname used) to hit a specific server?</p> <p>Current Configuration (Port Forwarding)</p> <pre><code>ourdomain.com:1234 -&gt; router/port-forwarding -&gt; SQL Server:1433 ourdomain.com:1235 -&gt; router/port-forwarding -&gt; Web Service 1:8081 ourdomain.com:1236 -&gt; router/port-forwarding -&gt; Web Service 2:8082 ourdomain.com:1237 -&gt; router/port-forwarding -&gt; Application Server:5410 </code></pre> <p>What I think I want:</p> <pre><code>sql.ourdomain.com:80 -&gt; ??? -&gt; SQL Server:1433 svc1.ourdomain.com:80 -&gt; ??? -&gt; Web Service 1:80 (host: svc1.ourdomain.com) svc2.ourdomain.com:80 -&gt; ??? -&gt; Web Service 2:80 (host: svc2.ourdomain.com) app.ourdomain.com:80 -&gt; ??? -&gt; Application Server:5410 </code></pre> <p>The (host: xxx) is where I would specify the host in the IIS website configuration.</p> <p>There will be some instances where port-forwarding is necessary, but it's not ideal for every instance. I want to remember meaningful names, not arbitrary port numbers.</p> <p>If what I'm asking here is completely ridiculous, well, thanks for reading. I'm just looking for some direction.</p> <p>Thanks!</p> <p>&lt;edit&gt;</p> <p><strong>12:01 am PDT 4/19/2012</strong></p> <p>Sorry, let me clarify a few things.</p> <ol> <li>We only have a single static public IP address. </li> <li>Assume that we can acquire / setup the necessary hardware / software to achieve this.</li> </ol> <p>If what it comes down to is that we need to buy some enterprise level routing hardware, that's just what it takes. I know this has to be possible because at my last job, we had 40 or 50 domains all pointed to the same IP that routed to different servers once inside the internal network. :/ Or at least that's what happened to the best of my knowledge.</p> <p>I actually called them up today and asked them, but the main dude who set it all up quit.</p> <p>I'm really pushing for us to just get our crap out into the cloud, since no one wants to hire a network engineer or systems analyst, much less build a data center.</p> <p>&lt;/edit&gt;</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload