how to forward all incoming traffic to new server

we're getting ready to take our old web server offline and replace with a
new
one. the new server will be hosted from a different city, so we're getting
an entirely new IP. once we've set up the new box and replicated all the
sites and databases, we need to be able to switch everything over in an
instant, pointing all incoming requests to the old server's IP to the new
server's IP. it's been suggested that i look into changing the DNS zone file
of the original server, but i'm having a hard time finding the file and info
on how to edit this.

can anybody point me if the right direction?

tks

Hi,
Changing the WWW record in DNS will not switch it over immediately as it
will take up to 3 days for all the DNS servers around the world to invalidate
their caches.
Set up the new web server to respond to say www2.mydomain.com
then set up a redirect on your old server to the new server at
www2.mydomain.com.
So all requests initially come to the old server at www.mydomain.com but are
redirected to the new one.
Then change your WWW record to point to the new server and after 3 or so
days you can decommission the old server.


"Dica" wrote:

> we're getting ready to take our old web server offline and replace with a
> new
> one. the new server will be hosted from a different city, so we're getting
> an entirely new IP. once we've set up the new box and replicated all the
> sites and databases, we need to be able to switch everything over in an
> instant, pointing all incoming requests to the old server's IP to the new
> server's IP. it's been suggested that i look into changing the DNS zone file
> of the original server, but i'm having a hard time finding the file and info
> on how to edit this.
>
> can anybody point me if the right direction?
>
> tks
>
>
>

"Wendel Hamilton" <(E-Mail Removed)> wrote in
message news7D70110-05AA-4E77-9B4A-(E-Mail Removed)...
> Hi,
> Changing the WWW record in DNS will not switch it over immediately as it
> will take up to 3 days for all the DNS servers around the world to
invalidate
> their caches.
> Set up the new web server to respond to say www2.mydomain.com
> then set up a redirect on your old server to the new server at
> www2.mydomain.com.
> So all requests initially come to the old server at www.mydomain.com but
are
> redirected to the new one.
> Then change your WWW record to point to the new server and after 3 or so
> days you can decommission the old server.

thanks wendel. that might work for a single site, but the old server hosts
about 100 or more sites and i think it's going to take too long to set that
up for each site. isn't there a simpler way to deal with this? i'd like to
approach the problem at the root level. is there a way to configure the
network cards themselves to redirect all TCP/IP traffic to the new box?

>
>
> "Dica" wrote:
>
> > we're getting ready to take our old web server offline and replace with
a
> > new
> > one. the new server will be hosted from a different city, so we're
getting
> > an entirely new IP. once we've set up the new box and replicated all the
> > sites and databases, we need to be able to switch everything over in an
> > instant, pointing all incoming requests to the old server's IP to the
new
> > server's IP. it's been suggested that i look into changing the DNS zone
file
> > of the original server, but i'm having a hard time finding the file and
info
> > on how to edit this.
> >
> > can anybody point me if the right direction?
> >
> > tks
> >
> >
> >

Hi,
What you need is a web or port proxy that can forward all the http requests
to the new server. see http://www.boutell.com/rinetd/
If the new server is internal to your network then you could use ISA server.
You may be able to redirect in IIS for all webs http://www to http://www2$V
(I think)
But it’s still a lot of work.
See
http://www.microsoft.com/technet/pro...383b1bb08.mspx



"Dica" wrote:

>
> "Wendel Hamilton" <(E-Mail Removed)> wrote in
> message news7D70110-05AA-4E77-9B4A-(E-Mail Removed)...
> > Hi,
> > Changing the WWW record in DNS will not switch it over immediately as it
> > will take up to 3 days for all the DNS servers around the world to
> invalidate
> > their caches.
> > Set up the new web server to respond to say www2.mydomain.com
> > then set up a redirect on your old server to the new server at
> > www2.mydomain.com.
> > So all requests initially come to the old server at www.mydomain.com but
> are
> > redirected to the new one.
> > Then change your WWW record to point to the new server and after 3 or so
> > days you can decommission the old server.
>
> thanks wendel. that might work for a single site, but the old server hosts
> about 100 or more sites and i think it's going to take too long to set that
> up for each site. isn't there a simpler way to deal with this? i'd like to
> approach the problem at the root level. is there a way to configure the
> network cards themselves to redirect all TCP/IP traffic to the new box?
>
> >
> >
> > "Dica" wrote:
> >
> > > we're getting ready to take our old web server offline and replace with
> a
> > > new
> > > one. the new server will be hosted from a different city, so we're
> getting
> > > an entirely new IP. once we've set up the new box and replicated all the
> > > sites and databases, we need to be able to switch everything over in an
> > > instant, pointing all incoming requests to the old server's IP to the
> new
> > > server's IP. it's been suggested that i look into changing the DNS zone
> file
> > > of the original server, but i'm having a hard time finding the file and
> info
> > > on how to edit this.
> > >
> > > can anybody point me if the right direction?
> > >
> > > tks
> > >
> > >
> > >
>
>
>

"Wendel Hamilton" <(E-Mail Removed)> wrote in
message news:C660AF13-5159-40CC-879C-(E-Mail Removed)...
> Hi,
> What you need is a web or port proxy that can forward all the http
requests
> to the new server. see http://www.boutell.com/rinetd/

wow, that's a killer app. i've been playing with it and it looks like it
should do the trick. thanks for the tip.

the only thing i'm not sure about is where exactly the domain names will
forward too. the rinetd app forwards all incoming traffic to the IP i
specify. so, if i have a site called 'acme.com' on the original box, a
request comes in for that site and rinetd forwards the request to the
specified ip address, does that mean that the new server will serve up the
'acme.com' site, or the default web site?

> If the new server is internal to your network then you could use ISA
server.
> You may be able to redirect in IIS for all webs http://www to
http://www2$V
> (I think)
> But it's still a lot of work.
> See
>
http://www.microsoft.com/technet/pro...383b1bb08.mspx
>
>
>
> "Dica" wrote:
>
> >
> > "Wendel Hamilton" <(E-Mail Removed)> wrote in
> > message news7D70110-05AA-4E77-9B4A-(E-Mail Removed)...
> > > Hi,
> > > Changing the WWW record in DNS will not switch it over immediately as
it
> > > will take up to 3 days for all the DNS servers around the world to
> > invalidate
> > > their caches.
> > > Set up the new web server to respond to say www2.mydomain.com
> > > then set up a redirect on your old server to the new server at
> > > www2.mydomain.com.
> > > So all requests initially come to the old server at www.mydomain.com
but
> > are
> > > redirected to the new one.
> > > Then change your WWW record to point to the new server and after 3 or
so
> > > days you can decommission the old server.
> >
> > thanks wendel. that might work for a single site, but the old server
hosts
> > about 100 or more sites and i think it's going to take too long to set
that
> > up for each site. isn't there a simpler way to deal with this? i'd like
to
> > approach the problem at the root level. is there a way to configure the
> > network cards themselves to redirect all TCP/IP traffic to the new box?
> >
> > >
> > >
> > > "Dica" wrote:
> > >
> > > > we're getting ready to take our old web server offline and replace
with
> > a
> > > > new
> > > > one. the new server will be hosted from a different city, so we're
> > getting
> > > > an entirely new IP. once we've set up the new box and replicated all
the
> > > > sites and databases, we need to be able to switch everything over in
an
> > > > instant, pointing all incoming requests to the old server's IP to
the
> > new
> > > > server's IP. it's been suggested that i look into changing the DNS
zone
> > file
> > > > of the original server, but i'm having a hard time finding the file
and
> > info
> > > > on how to edit this.
> > > >
> > > > can anybody point me if the right direction?
> > > >
> > > > tks
> > > >
> > > >
> > > >
> >
> >
> >

Hi,
It will serve acme.com
Sorry for the delayed reply I've been run off my feet the last couple of days.


"Dica" wrote:

>
> "Wendel Hamilton" <(E-Mail Removed)> wrote in
> message news:C660AF13-5159-40CC-879C-(E-Mail Removed)...
> > Hi,
> > What you need is a web or port proxy that can forward all the http
> requests
> > to the new server. see http://www.boutell.com/rinetd/
>
> wow, that's a killer app. i've been playing with it and it looks like it
> should do the trick. thanks for the tip.
>
> the only thing i'm not sure about is where exactly the domain names will
> forward too. the rinetd app forwards all incoming traffic to the IP i
> specify. so, if i have a site called 'acme.com' on the original box, a
> request comes in for that site and rinetd forwards the request to the
> specified ip address, does that mean that the new server will serve up the
> 'acme.com' site, or the default web site?
>
> > If the new server is internal to your network then you could use ISA
> server.
> > You may be able to redirect in IIS for all webs http://www to
> http://www2$V
> > (I think)
> > But it's still a lot of work.
> > See
> >
> http://www.microsoft.com/technet/pro...383b1bb08.mspx
> >
> >
> >
> > "Dica" wrote:
> >
> > >
> > > "Wendel Hamilton" <(E-Mail Removed)> wrote in
> > > message news7D70110-05AA-4E77-9B4A-(E-Mail Removed)...
> > > > Hi,
> > > > Changing the WWW record in DNS will not switch it over immediately as
> it
> > > > will take up to 3 days for all the DNS servers around the world to
> > > invalidate
> > > > their caches.
> > > > Set up the new web server to respond to say www2.mydomain.com
> > > > then set up a redirect on your old server to the new server at
> > > > www2.mydomain.com.
> > > > So all requests initially come to the old server at www.mydomain.com
> but
> > > are
> > > > redirected to the new one.
> > > > Then change your WWW record to point to the new server and after 3 or
> so
> > > > days you can decommission the old server.
> > >
> > > thanks wendel. that might work for a single site, but the old server
> hosts
> > > about 100 or more sites and i think it's going to take too long to set
> that
> > > up for each site. isn't there a simpler way to deal with this? i'd like
> to
> > > approach the problem at the root level. is there a way to configure the
> > > network cards themselves to redirect all TCP/IP traffic to the new box?
> > >
> > > >
> > > >
> > > > "Dica" wrote:
> > > >
> > > > > we're getting ready to take our old web server offline and replace
> with
> > > a
> > > > > new
> > > > > one. the new server will be hosted from a different city, so we're
> > > getting
> > > > > an entirely new IP. once we've set up the new box and replicated all
> the
> > > > > sites and databases, we need to be able to switch everything over in
> an
> > > > > instant, pointing all incoming requests to the old server's IP to
> the
> > > new
> > > > > server's IP. it's been suggested that i look into changing the DNS
> zone
> > > file
> > > > > of the original server, but i'm having a hard time finding the file
> and
> > > info
> > > > > on how to edit this.
> > > > >
> > > > > can anybody point me if the right direction?
> > > > >
> > > > > tks
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>

"Wendel Hamilton" <(E-Mail Removed)> wrote in
message news:F2C86F2F-9C54-4063-BBB4-(E-Mail Removed)...
> Hi,
> It will serve acme.com
> Sorry for the delayed reply I've been run off my feet the last couple of
days.

no worries. thanks again.


>
>
> "Dica" wrote:
>
> >
> > "Wendel Hamilton" <(E-Mail Removed)> wrote in
> > message news:C660AF13-5159-40CC-879C-(E-Mail Removed)...
> > > Hi,
> > > What you need is a web or port proxy that can forward all the http
> > requests
> > > to the new server. see http://www.boutell.com/rinetd/
> >
> > wow, that's a killer app. i've been playing with it and it looks like it
> > should do the trick. thanks for the tip.
> >
> > the only thing i'm not sure about is where exactly the domain names will
> > forward too. the rinetd app forwards all incoming traffic to the IP i
> > specify. so, if i have a site called 'acme.com' on the original box, a
> > request comes in for that site and rinetd forwards the request to the
> > specified ip address, does that mean that the new server will serve up
the
> > 'acme.com' site, or the default web site?
> >
> > > If the new server is internal to your network then you could use ISA
> > server.
> > > You may be able to redirect in IIS for all webs http://www to
> > http://www2$V
> > > (I think)
> > > But it's still a lot of work.
> > > See
> > >
> >
http://www.microsoft.com/technet/pro...383b1bb08.mspx
> > >
> > >
> > >
> > > "Dica" wrote:
> > >
> > > >
> > > > "Wendel Hamilton" <(E-Mail Removed)> wrote
in
> > > > message news7D70110-05AA-4E77-9B4A-(E-Mail Removed)...
> > > > > Hi,
> > > > > Changing the WWW record in DNS will not switch it over immediately
as
> > it
> > > > > will take up to 3 days for all the DNS servers around the world to
> > > > invalidate
> > > > > their caches.
> > > > > Set up the new web server to respond to say www2.mydomain.com
> > > > > then set up a redirect on your old server to the new server at
> > > > > www2.mydomain.com.
> > > > > So all requests initially come to the old server at
www.mydomain.com
> > but
> > > > are
> > > > > redirected to the new one.
> > > > > Then change your WWW record to point to the new server and after 3
or
> > so
> > > > > days you can decommission the old server.
> > > >
> > > > thanks wendel. that might work for a single site, but the old server
> > hosts
> > > > about 100 or more sites and i think it's going to take too long to
set
> > that
> > > > up for each site. isn't there a simpler way to deal with this? i'd
like
> > to
> > > > approach the problem at the root level. is there a way to configure
the
> > > > network cards themselves to redirect all TCP/IP traffic to the new
box?
> > > >
> > > > >
> > > > >
> > > > > "Dica" wrote:
> > > > >
> > > > > > we're getting ready to take our old web server offline and
replace
> > with
> > > > a
> > > > > > new
> > > > > > one. the new server will be hosted from a different city, so
we're
> > > > getting
> > > > > > an entirely new IP. once we've set up the new box and replicated
all
> > the
> > > > > > sites and databases, we need to be able to switch everything
over in
> > an
> > > > > > instant, pointing all incoming requests to the old server's IP
to
> > the
> > > > new
> > > > > > server's IP. it's been suggested that i look into changing the
DNS
> > zone
> > > > file
> > > > > > of the original server, but i'm having a hard time finding the
file
> > and
> > > > info
> > > > > > on how to edit this.
> > > > > >
> > > > > > can anybody point me if the right direction?
> > > > > >
> > > > > > tks
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >