DNS and Server move

G

Guest

Guest
Archived from groups: microsoft.public.win2000.dns (More info?)

Hi

I am planning on moving a couple of servers to a new location, and therefore
each server will have new IP addresses.

What I want to avoid as much as possible is downtime. There will be the
downtime while I physically move the servers, but I would like to limit the
issue with the DNS update causing longer downtime.

There is only the HTTP web service I need to ensure is limited in downtime,
so is it possible to forward all traffic from the old IP to the new IP, and
keep the host header data intact? This is because we have a couple of
hundred websites on virtual host headers on a couple of IP's. So
www.domain1.com and www.domain2.com on IP 123.123.123.123 relays the request
to the new IP 234.234.234.234 etc..

Any help is much appreciated

thanks

Mark
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.dns (More info?)

Will there still be a web server answering on 123.123.123.123 and doing the
redirection? If ys, then this would work. If I were doing it, I'd be
bringing down the TTL for all the web sites very very low BEFORE I actually
move the servers.

--


Sincerely,

Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"Mark Roberts" <mark@freshegg_nospam_.co.uk> wrote in message
news:OJPgdAh1EHA.1292@TK2MSFTNGP10.phx.gbl...
> Hi
>
> I am planning on moving a couple of servers to a new location, and
therefore
> each server will have new IP addresses.
>
> What I want to avoid as much as possible is downtime. There will be the
> downtime while I physically move the servers, but I would like to limit
the
> issue with the DNS update causing longer downtime.
>
> There is only the HTTP web service I need to ensure is limited in
downtime,
> so is it possible to forward all traffic from the old IP to the new IP,
and
> keep the host header data intact? This is because we have a couple of
> hundred websites on virtual host headers on a couple of IP's. So
> www.domain1.com and www.domain2.com on IP 123.123.123.123 relays the
request
> to the new IP 234.234.234.234 etc..
>
> Any help is much appreciated
>
> thanks
>
> Mark
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.dns (More info?)

The problem is the servers are being physically moved from 1 datacentre to
another, and therefore will not have luxury of migration. I am going to be
bringing down the TTL, but was hoping to find a way of maybe proxying the
TCP requests from 1 IP to the new IP. So far not found anything that could
do this.

Mark

"Deji Akomolafe" <noemail@akomolafe.dotcom> wrote in message
news:%23%23J7fti1EHA.2624@TK2MSFTNGP11.phx.gbl...
> Will there still be a web server answering on 123.123.123.123 and doing
> the
> redirection? If ys, then this would work. If I were doing it, I'd be
> bringing down the TTL for all the web sites very very low BEFORE I
> actually
> move the servers.
>
> --
>
>
> Sincerely,
>
> Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
> Microsoft MVP - Directory Services
> www.readymaids.com - we know IT
> www.akomolafe.com
> Do you now realize that Today is the Tomorrow you were worried about
> Yesterday? -anon
> "Mark Roberts" <mark@freshegg_nospam_.co.uk> wrote in message
> news:OJPgdAh1EHA.1292@TK2MSFTNGP10.phx.gbl...
>> Hi
>>
>> I am planning on moving a couple of servers to a new location, and
> therefore
>> each server will have new IP addresses.
>>
>> What I want to avoid as much as possible is downtime. There will be the
>> downtime while I physically move the servers, but I would like to limit
> the
>> issue with the DNS update causing longer downtime.
>>
>> There is only the HTTP web service I need to ensure is limited in
> downtime,
>> so is it possible to forward all traffic from the old IP to the new IP,
> and
>> keep the host header data intact? This is because we have a couple of
>> hundred websites on virtual host headers on a couple of IP's. So
>> www.domain1.com and www.domain2.com on IP 123.123.123.123 relays the
> request
>> to the new IP 234.234.234.234 etc..
>>
>> Any help is much appreciated
>>
>> thanks
>>
>> Mark
>>
>>
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.dns (More info?)

>>but was hoping to find a way of maybe proxying the TCP requests from 1 IP
to the new IP.

That's what I meant when I asked if there would be a web server at the old
address doing the redirect to the new address. If you have a box at the old
address, then you could add the 123.123.123.123 IP to the box, then create
redirections on that box to point to the original server at the new address.

--


Sincerely,

Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"Mark Roberts" <mark@freshegg_nospam_.co.uk> wrote in message
news:OiHv$hj1EHA.2608@TK2MSFTNGP10.phx.gbl...
> The problem is the servers are being physically moved from 1 datacentre to
> another, and therefore will not have luxury of migration. I am going to be
> bringing down the TTL, but was hoping to find a way of maybe proxying the
> TCP requests from 1 IP to the new IP. So far not found anything that could
> do this.
>
> Mark
>
> "Deji Akomolafe" <noemail@akomolafe.dotcom> wrote in message
> news:%23%23J7fti1EHA.2624@TK2MSFTNGP11.phx.gbl...
> > Will there still be a web server answering on 123.123.123.123 and doing
> > the
> > redirection? If ys, then this would work. If I were doing it, I'd be
> > bringing down the TTL for all the web sites very very low BEFORE I
> > actually
> > move the servers.
> >
> > --
> >
> >
> > Sincerely,
> >
> > Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
> > Microsoft MVP - Directory Services
> > www.readymaids.com - we know IT
> > www.akomolafe.com
> > Do you now realize that Today is the Tomorrow you were worried about
> > Yesterday? -anon
> > "Mark Roberts" <mark@freshegg_nospam_.co.uk> wrote in message
> > news:OJPgdAh1EHA.1292@TK2MSFTNGP10.phx.gbl...
> >> Hi
> >>
> >> I am planning on moving a couple of servers to a new location, and
> > therefore
> >> each server will have new IP addresses.
> >>
> >> What I want to avoid as much as possible is downtime. There will be the
> >> downtime while I physically move the servers, but I would like to limit
> > the
> >> issue with the DNS update causing longer downtime.
> >>
> >> There is only the HTTP web service I need to ensure is limited in
> > downtime,
> >> so is it possible to forward all traffic from the old IP to the new IP,
> > and
> >> keep the host header data intact? This is because we have a couple of
> >> hundred websites on virtual host headers on a couple of IP's. So
> >> www.domain1.com and www.domain2.com on IP 123.123.123.123 relays the
> > request
> >> to the new IP 234.234.234.234 etc..
> >>
> >> Any help is much appreciated
> >>
> >> thanks
> >>
> >> Mark
> >>
> >>
> >
> >
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.dns (More info?)

I can put a machine in at the old location, and give it the old IP address
123.123.123.123, but how and using what can i do redirects to the new ip
234.234.234.234, keeping the headers in place so IIS can serve the right
site?

thanks for your help on this Deji

"Deji Akomolafe" <noemail@akomolafe.dotcom> wrote in message
news:O9dfWVm1EHA.1400@TK2MSFTNGP11.phx.gbl...
>>>but was hoping to find a way of maybe proxying the TCP requests from 1 IP
> to the new IP.
>
> That's what I meant when I asked if there would be a web server at the old
> address doing the redirect to the new address. If you have a box at the
> old
> address, then you could add the 123.123.123.123 IP to the box, then create
> redirections on that box to point to the original server at the new
> address.
>
> --
>
>
> Sincerely,
>
> Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
> Microsoft MVP - Directory Services
> www.readymaids.com - we know IT
> www.akomolafe.com
> Do you now realize that Today is the Tomorrow you were worried about
> Yesterday? -anon
> "Mark Roberts" <mark@freshegg_nospam_.co.uk> wrote in message
> news:OiHv$hj1EHA.2608@TK2MSFTNGP10.phx.gbl...
>> The problem is the servers are being physically moved from 1 datacentre
>> to
>> another, and therefore will not have luxury of migration. I am going to
>> be
>> bringing down the TTL, but was hoping to find a way of maybe proxying the
>> TCP requests from 1 IP to the new IP. So far not found anything that
>> could
>> do this.
>>
>> Mark
>>
>> "Deji Akomolafe" <noemail@akomolafe.dotcom> wrote in message
>> news:%23%23J7fti1EHA.2624@TK2MSFTNGP11.phx.gbl...
>> > Will there still be a web server answering on 123.123.123.123 and doing
>> > the
>> > redirection? If ys, then this would work. If I were doing it, I'd be
>> > bringing down the TTL for all the web sites very very low BEFORE I
>> > actually
>> > move the servers.
>> >
>> > --
>> >
>> >
>> > Sincerely,
>> >
>> > Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
>> > Microsoft MVP - Directory Services
>> > www.readymaids.com - we know IT
>> > www.akomolafe.com
>> > Do you now realize that Today is the Tomorrow you were worried about
>> > Yesterday? -anon
>> > "Mark Roberts" <mark@freshegg_nospam_.co.uk> wrote in message
>> > news:OJPgdAh1EHA.1292@TK2MSFTNGP10.phx.gbl...
>> >> Hi
>> >>
>> >> I am planning on moving a couple of servers to a new location, and
>> > therefore
>> >> each server will have new IP addresses.
>> >>
>> >> What I want to avoid as much as possible is downtime. There will be
>> >> the
>> >> downtime while I physically move the servers, but I would like to
>> >> limit
>> > the
>> >> issue with the DNS update causing longer downtime.
>> >>
>> >> There is only the HTTP web service I need to ensure is limited in
>> > downtime,
>> >> so is it possible to forward all traffic from the old IP to the new
>> >> IP,
>> > and
>> >> keep the host header data intact? This is because we have a couple of
>> >> hundred websites on virtual host headers on a couple of IP's. So
>> >> www.domain1.com and www.domain2.com on IP 123.123.123.123 relays the
>> > request
>> >> to the new IP 234.234.234.234 etc..
>> >>
>> >> Any help is much appreciated
>> >>
>> >> thanks
>> >>
>> >> Mark
>> >>
>> >>
>> >
>> >
>>
>>
>
>
 
G

Guest

Guest
Archived from groups: microsoft.public.win2000.dns (More info?)

Sorry for the late response. The new server will run web services (IIS or
whatever). Then you will simply create a website on the new server (give the
web site the same name as the one you had on te original server). Create an
html like the one listed below:

<html>
<head>
<meta http-equiv="refresh" content="30;url=http://new.ip.add.ress/">
<title>
We have moved
</title>
</head>
<body>
We have just moved to a new, better home in order to be able to provide more
robust services to you, our loyal customers. <br>
We will now forward you to our new home in 30 seconds.<br>
Thank you
</body>
</html>

name this index.html or default.html or whatever the default doc for your
web site is called.

You can also do the redirection right from the website "home directory"
properties in IIS, but that is usually less friendly (chatty ;))
--


Sincerely,

Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"Mark Roberts" <mark@freshegg_nospam_.co.uk> wrote in message
news:O$Wk1is1EHA.2804@TK2MSFTNGP15.phx.gbl...
> I can put a machine in at the old location, and give it the old IP address
> 123.123.123.123, but how and using what can i do redirects to the new ip
> 234.234.234.234, keeping the headers in place so IIS can serve the right
> site?
>
> thanks for your help on this Deji
>
> "Deji Akomolafe" <noemail@akomolafe.dotcom> wrote in message
> news:O9dfWVm1EHA.1400@TK2MSFTNGP11.phx.gbl...
> >>>but was hoping to find a way of maybe proxying the TCP requests from 1
IP
> > to the new IP.
> >
> > That's what I meant when I asked if there would be a web server at the
old
> > address doing the redirect to the new address. If you have a box at the
> > old
> > address, then you could add the 123.123.123.123 IP to the box, then
create
> > redirections on that box to point to the original server at the new
> > address.
> >
> > --
> >
> >
> > Sincerely,
> >
> > Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
> > Microsoft MVP - Directory Services
> > www.readymaids.com - we know IT
> > www.akomolafe.com
> > Do you now realize that Today is the Tomorrow you were worried about
> > Yesterday? -anon
> > "Mark Roberts" <mark@freshegg_nospam_.co.uk> wrote in message
> > news:OiHv$hj1EHA.2608@TK2MSFTNGP10.phx.gbl...
> >> The problem is the servers are being physically moved from 1 datacentre
> >> to
> >> another, and therefore will not have luxury of migration. I am going to
> >> be
> >> bringing down the TTL, but was hoping to find a way of maybe proxying
the
> >> TCP requests from 1 IP to the new IP. So far not found anything that
> >> could
> >> do this.
> >>
> >> Mark
> >>
> >> "Deji Akomolafe" <noemail@akomolafe.dotcom> wrote in message
> >> news:%23%23J7fti1EHA.2624@TK2MSFTNGP11.phx.gbl...
> >> > Will there still be a web server answering on 123.123.123.123 and
doing
> >> > the
> >> > redirection? If ys, then this would work. If I were doing it, I'd be
> >> > bringing down the TTL for all the web sites very very low BEFORE I
> >> > actually
> >> > move the servers.
> >> >
> >> > --
> >> >
> >> >
> >> > Sincerely,
> >> >
> >> > Dèjì Akómöláfé, MCSE+M MCSA+M MCP+I
> >> > Microsoft MVP - Directory Services
> >> > www.readymaids.com - we know IT
> >> > www.akomolafe.com
> >> > Do you now realize that Today is the Tomorrow you were worried about
> >> > Yesterday? -anon
> >> > "Mark Roberts" <mark@freshegg_nospam_.co.uk> wrote in message
> >> > news:OJPgdAh1EHA.1292@TK2MSFTNGP10.phx.gbl...
> >> >> Hi
> >> >>
> >> >> I am planning on moving a couple of servers to a new location, and
> >> > therefore
> >> >> each server will have new IP addresses.
> >> >>
> >> >> What I want to avoid as much as possible is downtime. There will be
> >> >> the
> >> >> downtime while I physically move the servers, but I would like to
> >> >> limit
> >> > the
> >> >> issue with the DNS update causing longer downtime.
> >> >>
> >> >> There is only the HTTP web service I need to ensure is limited in
> >> > downtime,
> >> >> so is it possible to forward all traffic from the old IP to the new
> >> >> IP,
> >> > and
> >> >> keep the host header data intact? This is because we have a couple
of
> >> >> hundred websites on virtual host headers on a couple of IP's. So
> >> >> www.domain1.com and www.domain2.com on IP 123.123.123.123 relays the
> >> > request
> >> >> to the new IP 234.234.234.234 etc..
> >> >>
> >> >> Any help is much appreciated
> >> >>
> >> >> thanks
> >> >>
> >> >> Mark
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>