|
Home > Archive > IIS Server > January 2004 > Forwarding problem.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Forwarding problem.
|
|
| GriffithsJ 2004-01-24, 1:38 am |
| I have a customer's website that I have to move from one webserver (serverA)
to another (serverB) this weekend.
Their website had a DNS record pointing to the main IP address of serverA.
We bound a new IP address to serverA and requested that the DNS record for
this customer's URL be changed to the new IP address. The idea is that this
information has had time to propagate throughout the world and this weekend
we can safely unbind the IP address from serverA and bind it to serverB and
everything will work.
However, we've just discovered that the people who change our DNS records
did not actually change the record but simply added a new record. This
means that a nslookup on the customer's URL returns two IP addresses, the
one we can migrate between machines and the one that we can't.
We've asked them to delete the DNS record and they say that they'll
definitely do it within 5 working days, so including propagation time we
could be having requests to the wrong IP address for up to 7 days.
What we want to do is to ensure that any requests to the old machine are
automatically forwarded to the website on the new machine. The old machine
will still continue to host several other customers' websites.
Any suggestions?
We're using IIS on Windows2000. Web pages are almost exclusively ASP (not
..Net) and most requests come in the form
'http://customer.domain.co.uk/page.asp?a=b&c=d&e=f'.
Many many thanks to anyone who can help!
Thanks
Griff
| |
| Roger Abell [MVP] 2004-01-24, 1:38 am |
| IIS allows you to define a premanent redirection, in the properties
of the website. You could use this until the stale DNS record has
aged out.
BTW you need to wait, after the DNS change, not just the time
for the propagation delay, but also a time equal to the TTL (time
to live) on the record, as the record with the old IP is allowed to
be cached and used downstream for up to the TTL.
"GriffithsJ" <GriffithsJ_520@hotmail.com> wrote in message
news:eb7I9Qq1DHA.2408@tk2msftngp13.phx.gbl...quote:
> I have a customer's website that I have to move from one webserver
(serverA)quote:
> to another (serverB) this weekend.
>
> Their website had a DNS record pointing to the main IP address of serverA.
> We bound a new IP address to serverA and requested that the DNS record for
> this customer's URL be changed to the new IP address. The idea is that
thisquote:
> information has had time to propagate throughout the world and this
weekendquote:
> we can safely unbind the IP address from serverA and bind it to serverB
andquote:
> everything will work.
>
> However, we've just discovered that the people who change our DNS records
> did not actually change the record but simply added a new record. This
> means that a nslookup on the customer's URL returns two IP addresses, the
> one we can migrate between machines and the one that we can't.
>
> We've asked them to delete the DNS record and they say that they'll
> definitely do it within 5 working days, so including propagation time we
> could be having requests to the wrong IP address for up to 7 days.
>
> What we want to do is to ensure that any requests to the old machine are
> automatically forwarded to the website on the new machine. The old
machinequote:
> will still continue to host several other customers' websites.
>
> Any suggestions?
>
> We're using IIS on Windows2000. Web pages are almost exclusively ASP (not
> .Net) and most requests come in the form
> 'http://customer.domain.co.uk/page.asp?a=b&c=d&e=f'.
>
> Many many thanks to anyone who can help!
>
> Thanks
>
> Griff
>
>
|
|
|
|
|