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.
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. 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 r
> 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
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
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
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 logg
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.
http://www.do
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 log
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.
http://www.d
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
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, trus
> 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
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
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"
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
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, tru
> 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
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
squi
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
20 matches
Mail list logo
