|
Look like the best approach to me. You may also want to bind this IP address to one particular interface if you have more than one on the system. I prefer to have internal telnet to one IP and interface and the web/mail/... to other IPs and interface. This can be in different subnets and different physical switches, hub and routers as well. Christopher K. Bipes mailto:ChrisB@Cross-Check.com Sr. Programmer/Analyst mailto:Chris_Bipes@Yahoo.com CrossCheck, Inc. http://www.cross-check.com 6119 State Farm Drive Phone: 707 586-0551 x 1102 Rohnert Park CA 94928 Fax: 707 586-1884 If consistency is the hobgoblin of little minds, only geniuses work here. Karen Herbelin - Readers Digest 3/2000 -----Original Message----- From: Stone, Brad V (TC) [mailto:bvstone@taylorcorp.com] Sent: Monday, May 08, 2000 8:30 AM To: 'MIDRANGE-L@midrange.com' Subject: one external IP to multiple internal IPs? Ideas? I am looking for ideas. We have an As/400 that we are using for web serving. Our network group has a router set up to route requests to it. This server will be serving multiple companies for customer service. What I would like to do ideally is set up an instance for each company (using BindSpecific) so that each of them can run in seperate jobs. Also, logging seperately is another reason I want to do this. What we plan on doing is making a subdomain for the companies that will route these requests to the AS/400. For example, company1.com will have a subdomain of cso.company1.com that will be routed a particular external IP address, then routed to the AS/400. Our network guys tell me they can only route IPs on a one to one basis, so to run multiple servers I would need an external IP for each company. So, here's what I want.. URL Ext. IP AS/400 IP cso.company1.com -> 218.1.1.2 -> 172.25.6.1 cso.company2.com -> 218.1.1.2 -> 172.25.6.2 etc.. etc.. Does anyone else have any better ideas? I know I can use virtual hosts and one IP address, but like I said, I'd rather keep them seperate. Brad> +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.