Search Again: Dealing with NAT From: Kirk Samuelson Date: Sunday, July 4, 1999 Time: 3:17: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?). So I can't use domain names for Web Server B. Or can I? Is there a workaround for this? TIA, Kirk

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