Re: Inherited ISP host configuration nightmare
Craig Sanders wrote: On Fri, Aug 18, 2000 at 01:07:52PM -0600, Kevin Blackham wrote: From what I understand here, you need a simple webserver on the Linux mail server (domain.com) that will redirect clients to www.domain.com, at least until you can get the customer base reconfigured. he's probably better off using squid on the linux box as an http accelerator. ... ... it's probably a lot simpler to just use a port redirector, to redirect all connections to port 80 on the linux box to port 80 on the NT server. ... it would be much better to leave things exactly as they are for now and configure a new linux server to do everything that the NT box is currently doingthen, when it is working, cut over to the linux box. ... Thanks for all the suggestions. A refresh on the current SNAFU is that all virtual domains are hosted on NT (probably half using Microswipe Front Cage) on an IP-per-domain basis. Because of email usage, all vdomain.com DNS requests are directed to the one Linux server IP address. The Linux box would have to properly redirect each http://vdomain.com; request on port 80 of the Linux system to the appropriate IP address on the NT box or to http://www.vdomain.com;. -- http://www.networksonline.com/service.htm ICQ #58278887
Re: Inherited ISP host configuration nightmare
On Fri, Aug 18, 2000 at 01:07:52PM -0600, Kevin Blackham wrote: From what I understand here, you need a simple webserver on the Linux mail server (domain.com) that will redirect clients to www.domain.com, at least until you can get the customer base reconfigured. Stick Apache on there and set your index.html with this tag in the header. META HTTP-EQUIV="refresh" CONTENT="0;URL=http://www.domain.com" he's probably better off using squid on the linux box as an http accelerator. much easier to configure, just set it up to accelerate for virtual domains and that's it. squid is also a lot faster and avoids the delays inherent in sending a redirect (browser queries apache, apache sends redirect, browser queries 2nd server). doing it with apache would require a redirect rule for each virtual domain - even then it's hard to see how it would workwhere is it going to redirect TO? if the linux box is www.domain.com, then there's no point in it redirecting to www.domain.com. actually, the same problem would occur with squid - but at least you can use a redirector with a bunch of simple rules to redirect from, say, www.domain.com to real.www.domain.com (and set up the DNS entries accordingly). that could be done with a single rule: as a perl regexp, that would be: s/www(.*)/real.www$1/ it's probably a lot simpler to just use a port redirector, to redirect all connections to port 80 on the linux box to port 80 on the NT server. this is a TCP level redirection, not an application level (http) redirect so there's little overhead/delay incurred. thinking more about it, there's a whole bunch of things like that which could go wrong. it's impossible to tell without a good knowledge of exactly how the current system(s) are set up. you can't make a viable migration plan until you know what kind of mess you're working with. it would be much better to leave things exactly as they are for now and configure a new linux server to do everything that the NT box is currently doingthen, when it is working, cut over to the linux box. alternatively, do this in conjunction with the port redirector idea above. first set up linux to redirect port 80, then set up apache on port 81 and copy the virtual hosts over to it. test well. when they're working on port 81, turn off the redirector and reconfigure apache to use port 80. after a week or so (when you know that you wont need to revert to the old setup because everything is working fine), recycle the NT box - format it and install debian. there's lots of ways of doing this, and lots of potential problems. the most important thing is to have a plan. think out what you're going to do, step-by-step before you do it. make backups and always give yourself a way to revert to the old setup in case of a mistake or unforeseen problem. proceed slowly and cautiously. don't panic. craig -- craig sanders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
he's probably better off using squid on the linux box as an http accelerator. much easier to configure, just set it up to accelerate for virtual domains and that's it. squid is also a lot faster and avoids the delays inherent in sending a redirect (browser queries apache, apache sends redirect, browser queries 2nd server). This is true and I like squid, I use it, but it runs the risk of not being transparent enough. You end up having to special case sites, and one of the things it can't do is M$ authentication. after a week or so (when you know that you wont need to revert to the old setup because everything is working fine), recycle the NT box - format it and install debian. Ah why wait... you know it's the only really long term solution *grin*... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
On Fri, Aug 18, 2000 at 01:07:52PM -0600, Kevin Blackham wrote: From what I understand here, you need a simple webserver on the Linux mail server (domain.com) that will redirect clients to www.domain.com, at least until you can get the customer base reconfigured. Stick Apache on there and set your index.html with this tag in the header. META HTTP-EQUIV=refresh CONTENT=0;URL=http://www.domain.com; he's probably better off using squid on the linux box as an http accelerator. much easier to configure, just set it up to accelerate for virtual domains and that's it. squid is also a lot faster and avoids the delays inherent in sending a redirect (browser queries apache, apache sends redirect, browser queries 2nd server). doing it with apache would require a redirect rule for each virtual domain - even then it's hard to see how it would workwhere is it going to redirect TO? if the linux box is www.domain.com, then there's no point in it redirecting to www.domain.com. actually, the same problem would occur with squid - but at least you can use a redirector with a bunch of simple rules to redirect from, say, www.domain.com to real.www.domain.com (and set up the DNS entries accordingly). that could be done with a single rule: as a perl regexp, that would be: s/www(.*)/real.www$1/ it's probably a lot simpler to just use a port redirector, to redirect all connections to port 80 on the linux box to port 80 on the NT server. this is a TCP level redirection, not an application level (http) redirect so there's little overhead/delay incurred. thinking more about it, there's a whole bunch of things like that which could go wrong. it's impossible to tell without a good knowledge of exactly how the current system(s) are set up. you can't make a viable migration plan until you know what kind of mess you're working with. it would be much better to leave things exactly as they are for now and configure a new linux server to do everything that the NT box is currently doingthen, when it is working, cut over to the linux box. alternatively, do this in conjunction with the port redirector idea above. first set up linux to redirect port 80, then set up apache on port 81 and copy the virtual hosts over to it. test well. when they're working on port 81, turn off the redirector and reconfigure apache to use port 80. after a week or so (when you know that you wont need to revert to the old setup because everything is working fine), recycle the NT box - format it and install debian. there's lots of ways of doing this, and lots of potential problems. the most important thing is to have a plan. think out what you're going to do, step-by-step before you do it. make backups and always give yourself a way to revert to the old setup in case of a mistake or unforeseen problem. proceed slowly and cautiously. don't panic. craig -- craig sanders
Re: Inherited ISP host configuration nightmare
he's probably better off using squid on the linux box as an http accelerator. much easier to configure, just set it up to accelerate for virtual domains and that's it. squid is also a lot faster and avoids the delays inherent in sending a redirect (browser queries apache, apache sends redirect, browser queries 2nd server). This is true and I like squid, I use it, but it runs the risk of not being transparent enough. You end up having to special case sites, and one of the things it can't do is M$ authentication. after a week or so (when you know that you wont need to revert to the old setup because everything is working fine), recycle the NT box - format it and install debian. Ah why wait... you know it's the only really long term solution *grin*...
Inherited ISP host configuration nightmare
Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of "domain.com" instead of "mail.domain.com". We need "domain.com" to resolve to the NT web server for "http://domain.com" requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
Gene, i dont think this is possible. There may be some tricks you can do with ipchains to forward packets from one port to another IP/port and get the job done, but it would probably be a kludge. You could also do this on your cisco, kinda like redirecting all traffic through the router to a squid server, or similar. Why dont you put up a simple web server on the linux box and then have them automatically transferred to the NT box (where the real web server/pages are located?) This would be very simple and could be done in a number of ways, and ways in which they were meant to be used? On Fri, 18 Aug 2000, Gene Grimm wrote: | Upon reviewing host configurations created by my predecessor, I | inherited a nightmare. DNS was misconfigured from the start, causing | dial-up clients to use a SMTP/POP3 hostname of "domain.com" instead of | "mail.domain.com". We need "domain.com" to resolve to the NT web server | for "http://domain.com" requests and to the Linux mail server for mail | client software. It will take a few months to migrate clients to a new | SMTP/POP3 host name. Does anyone know how to best handle this on the | Linux host in the interim? Many thanks in advance for any assistance. | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] | | -- ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 8:20am up 99 days, 14:23, 4 users, load average: 0.24, 0.17, 0.11 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
Upon reviewing host configurations created by my predecessor, I inherited a nightmare. I almost forgot to mention, we have about 40-60 virtual domains hosted via for both email and web services on these two machines. Is there some script that will handle this for all domains without having to configure each one individually? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
Gene, you need to be a little bit more specific. It sounds like you might be getting in a little over your head. You should probably do a little bit of reading before you go changing alot of stuff around, or you could have some pissed off customers to deal with... i know how much that sucks, trust me, you dont want to be there. I'll give you some links, and then you can tell me what you might be looking to do. Some questions first. Are the virtual domains on linux machine(s) or NT machine(s)? We host all our virtual domains on a linux box. Apache has virtual domain support built in, and you can even setup a virtual domain without using an IP with apache. We dont currently do this, but we plan to in the future. Currently we still setup our virtual domains with IP addresses. For the email, we use qmail, which works beautifully, securely, efficiently, and VERY easily with virtual domains. (as you can tell, i'm a qmail bigot) http://www.linux.org/docs/ldp/howto/Virtual-Services-HOWTO.html http://www.linux.org/docs/ldp/howto/VMailMgr-HOWTO.html On Fri, 18 Aug 2000, Gene Grimm wrote: | Upon reviewing host configurations created by my predecessor, I | inherited a nightmare. | | I almost forgot to mention, we have about 40-60 virtual domains hosted via for | both email and web services on these two machines. Is there some script that will | handle this for all domains without having to configure each one individually? | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] | | -- ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 8:30am up 99 days, 14:33, 4 users, load average: 0.35, 0.21, 0.15 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Inherited ISP host configuration nightmare
GG [...] DNS was misconfigured from the start, GG causing dial-up clients to use a SMTP/POP3 hostname of GG "domain.com" instead of "mail.domain.com". We need GG "domain.com" to resolve to the NT web server for GG "http://domain.com" requests and to the Linux mail server for GG mail client software. [...] No problem, (I alluded to this yesterday). Just run a web server on the linux machine and have it issue HTTP redirects from domain.com to www.domain.com. You could also port-forward, but I think the redirect is easier to get right (and less disruptive as you are getting it right). Apache would do just fine. The bigger picture: Maybe you want to bring in an experienced firefighter for while, learn from him and then take over? Good bosses usually like 'this is new, I'll need to learn' almost as much as they like 'sure, I can do it.' Yours in particular should by now. BM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
Gene, From what I understand here, you need a simple webserver on the Linux mail server (domain.com) that will redirect clients to www.domain.com, at least until you can get the customer base reconfigured. Stick Apache on there and set your index.html with this tag in the header. META HTTP-EQUIV="refresh" CONTENT="0;URL=http://www.domain.com" -- Kevin Blackham 801-539-0852 Domains Administrator, XMission Internet 877-XMISSION [EMAIL PROTECTED]877-964-7746 http://www.xmission.com/help On Fri, Aug 18, 2000 at 10:16:46AM -0400, Gene Grimm wrote: Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of "domain.com" instead of "mail.domain.com". We need "domain.com" to resolve to the NT web server for "http://domain.com" requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Inherited ISP host configuration nightmare
On Fri, 18 Aug 2000, Gene Grimm wrote: The easiest thing I can think of is ipportfw. Why not just forward the mail or http ports to the other machine. (probably the http in this case). Maybe setup a simple ip chain on the mail ports to keep track of how much data goes through them, or even logging the ips of the users who go through. (cross reference with access logs and you should have an idea of which clients to have your support department contact when they aren't too busy). Puts a little extra load on the linux box, but I am sure it can handle it. Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of "domain.com" instead of "mail.domain.com". We need "domain.com" to resolve to the NT web server for "http://domain.com" requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] --- J.R. Blain [EMAIL PROTECTED] http://www.top100.org [EMAIL PROTECTED] http://www.2kservices.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Inherited ISP host configuration nightmare
Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of domain.com instead of mail.domain.com. We need domain.com to resolve to the NT web server for http://domain.com; requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance.
Re: Inherited ISP host configuration nightmare
Gene, i dont think this is possible. There may be some tricks you can do with ipchains to forward packets from one port to another IP/port and get the job done, but it would probably be a kludge. You could also do this on your cisco, kinda like redirecting all traffic through the router to a squid server, or similar. Why dont you put up a simple web server on the linux box and then have them automatically transferred to the NT box (where the real web server/pages are located?) This would be very simple and could be done in a number of ways, and ways in which they were meant to be used? On Fri, 18 Aug 2000, Gene Grimm wrote: | Upon reviewing host configurations created by my predecessor, I | inherited a nightmare. DNS was misconfigured from the start, causing | dial-up clients to use a SMTP/POP3 hostname of domain.com instead of | mail.domain.com. We need domain.com to resolve to the NT web server | for http://domain.com; requests and to the Linux mail server for mail | client software. It will take a few months to migrate clients to a new | SMTP/POP3 host name. Does anyone know how to best handle this on the | Linux host in the interim? Many thanks in advance for any assistance. | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] | | -- ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 8:20am up 99 days, 14:23, 4 users, load average: 0.24, 0.17, 0.11
Re: Inherited ISP host configuration nightmare
Upon reviewing host configurations created by my predecessor, I inherited a nightmare. I almost forgot to mention, we have about 40-60 virtual domains hosted via for both email and web services on these two machines. Is there some script that will handle this for all domains without having to configure each one individually?
Re: Inherited ISP host configuration nightmare
Gene, you need to be a little bit more specific. It sounds like you might be getting in a little over your head. You should probably do a little bit of reading before you go changing alot of stuff around, or you could have some pissed off customers to deal with... i know how much that sucks, trust me, you dont want to be there. I'll give you some links, and then you can tell me what you might be looking to do. Some questions first. Are the virtual domains on linux machine(s) or NT machine(s)? We host all our virtual domains on a linux box. Apache has virtual domain support built in, and you can even setup a virtual domain without using an IP with apache. We dont currently do this, but we plan to in the future. Currently we still setup our virtual domains with IP addresses. For the email, we use qmail, which works beautifully, securely, efficiently, and VERY easily with virtual domains. (as you can tell, i'm a qmail bigot) http://www.linux.org/docs/ldp/howto/Virtual-Services-HOWTO.html http://www.linux.org/docs/ldp/howto/VMailMgr-HOWTO.html On Fri, 18 Aug 2000, Gene Grimm wrote: | Upon reviewing host configurations created by my predecessor, I | inherited a nightmare. | | I almost forgot to mention, we have about 40-60 virtual domains hosted via for | both email and web services on these two machines. Is there some script that will | handle this for all domains without having to configure each one individually? | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] | | -- ___ _ __ _ __ /___ ___ /__ John Gonzalez/Net.Tech __ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC! _ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052 /_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com [-[system info]---] 8:30am up 99 days, 14:33, 4 users, load average: 0.35, 0.21, 0.15
Re: Inherited ISP host configuration nightmare
On Fri, 18 Aug 2000, Gene Grimm wrote: The easiest thing I can think of is ipportfw. Why not just forward the mail or http ports to the other machine. (probably the http in this case). Maybe setup a simple ip chain on the mail ports to keep track of how much data goes through them, or even logging the ips of the users who go through. (cross reference with access logs and you should have an idea of which clients to have your support department contact when they aren't too busy). Puts a little extra load on the linux box, but I am sure it can handle it. Upon reviewing host configurations created by my predecessor, I inherited a nightmare. DNS was misconfigured from the start, causing dial-up clients to use a SMTP/POP3 hostname of domain.com instead of mail.domain.com. We need domain.com to resolve to the NT web server for http://domain.com; requests and to the Linux mail server for mail client software. It will take a few months to migrate clients to a new SMTP/POP3 host name. Does anyone know how to best handle this on the Linux host in the interim? Many thanks in advance for any assistance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --- J.R. Blain [EMAIL PROTECTED] http://www.top100.org [EMAIL PROTECTED] http://www.2kservices.com
