Re: Can I change the public IP of a website on dual wan router without losing customers?



"Ed" <edwardotis@xxxxxxxxx> wrote in message
news:1163717143.483419.124740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Not sure if this is the right forum, but here is my question.

Close enough....

Key point to answer your subject line is likely going to be:

TTL settings on the zone or individual records

We host a secure web application in house with address:
https://myapp.mydomain.com
Our main website is hosted by 1and1 web hosting.
http://www.mydomain.com
I setup 1and1's name servers to point the subdomain 'myapp', to the
public static IP of our T1 at the office. The web traffic is is then
forwarded by our Linksys RV082 router to our internal IIS 6 box hosting
the web application. Everything works great.

We are switching from the T1 to an SDSL solution. The RV082 router has
dual wan interface, so I can attach the SDSL to the 2nd wan port
without disrupting the T1. I then have two internet connections and two
public IP addresses. The 80 and 443 traffic is forwarded over either
wan interface to the the internal IIS 6 box hosting the web app.

So both IP addresses will be "live" and valid at the
same time during the switchover?

If so you will never have a network outage so you
only need to make sure there is no DNS issue with
clients (both other DNS servers and client machines)
caching your old DNS records LONGER than your
overlap period.

I want to make the name server switch to point
https://myapp.mydomain.com from the T1 IP to the SDSL IP without
disrupting any users of the web application. I realize that there is a
12 - 48 hour dns propagation delay when changing the IP's of a public
dns record.

That is ONLY an issue for whoever hosts your DNS records,
not a necessity. It is in additional to the TTL.

Usually you should have your public DNS at the registrar,
but YOU should actually be able to edit the records.

KEY:
At least ONE FULL "TTL period" before any changes you
should go CHANGE the TTL period to something reasonably
short on the DNS server. Do this for any specific records with
their own TLL that might be changed AND for the zone itself
if some of those records don't have specific TTL settings.

Doing this will ensure that nobody caches your records "too long".

However, given my setup, I believe that every user will
correctly get to my web application during the propagation period
because they will be sent to either the T1 or the SDSL public IP. A
given user session with the our web application will last about 30
minutes.

Yes.

Can anyone provide insight as to whether this scenario will work, or if
there are any potential problems?

As long as both addresses are live and you don't have
anyone caching the records or admin delays LONGER
than the overlap period then there should be no issue from
DNS.

BUT since you said "Secure" web service, watch out for
any problems with your CERTIFICATE for the web server
which might have the IP embedded into it.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Thanks,

Ed J.




.



Relevant Pages

  • Re: DNS signature failed to verify error
    ... In our last we discussed the need for there to be a NS record for each DNS ... Under the zone domain.local there is a delegation _msdcs which only has one ... _msdcs.domain.local is configured the "Replicate to all DNS servers in the AD ... Thanks for the DCDiag syntax suggestion. ...
    (microsoft.public.windows.server.dns)
  • Re: Windows 2008 DNS Secondary 2003 primary DNS zone
    ... I have a primary DNS zone "mydomain.com" running on a 2003 DC, ... we register our domain names with) All the DNS servers are AD domain ... When you have an AD integrated zone, the DNS data is stored in the actual AD database and is replicated to all DCs and will be available to any DC that has DNS installed, depending on the zone replication scope setting. ...
    (microsoft.public.windows.server.dns)
  • Re: 2 Questions...
    ... In one post you asked about the value of the empty root. ... With a multi-domain forest one has a few choices for DNS ... One could use standard zone transfer to these, ... as already stated or by having the DNS servers of corp forward to ...
    (microsoft.public.windows.server.dns)
  • Re: Question re: DNS forwarding best practices
    ... change rate of the root DNS zone's content. ... to a primary of the zone, so hopefully you have at least one ... as the case might allow) to the DNS servers of the root. ...
    (microsoft.public.windows.server.dns)
  • Re: sys vol check
    ... You've 3 DC DNS servers one in each Site with different subnets. ... You've A forward lookup Zone named CORP.DLECINC.COM and a reverse lookup ... The clients should use only their local DNSserver in ther NIC ...
    (microsoft.public.windows.server.active_directory)