Search Again: Re: Dealing with NAT From: Men & Mice Support Date: Sunday, July 4, 1999 Time: 10:32:00 am >Hi again. I'm on a DSL line which uses Network Address Translation to map >incoming requests to individual computers on my LAN. I have only one public >IP address for the router. NAT allows you to alias a real port (80) to a >private port (9001 for instance). Thus: > >166.90.75.31 -> Web Server A >166.90.75.31:9001 -> Web Server B > >This is all fine and dandy BUT dns records don't contain any port >information (do they?). That is correct. > So I can't use domain names for Web Server B. Or can >I? Is there a workaround for this? If I understand properly, in the above example, 166.90.75.31 is the public address, and web servers A and B are your physical machines behind the NAT proxy. If this is the case, the best you can do is to point all your domain names at your public address, and always use a port number to access web server B. So for domainA.com, you have a URL like http://www.domainA.com/, and for domain B, you have a URL like http://www.domainB.com:9001/. If someone types in www.domainB.com (without the port number), they'll get web server A. On server A, you can use WebSTAR's virtual host manager to map www.domainB.com to a redirect (raw) file, which will redirect them to www.domainB.com:9001. Your NAT server will route this to web server B. How's that for a workaround? ____________________________________________________________________ Chris Buxton Men & Mice cbuxton@menandmice.com http://www.menandmice.com

Messages In This Thread: Dealing with NAT by Kirk Samuelson on Jul 4, 1999 at 3:17:00 am Re: Dealing with NAT by Men & Mice Support on Jul 4, 1999 at 10:32:00 am Re: Dealing with NAT by Kirk Samuelson on Jul 4, 1999 at 4:05:00 pm