One person I spoke to outside this list suggested that I keep the old IP =
addresses and DNS mapping for our nameservers on our network even after =
we switch to the new backbone provider. He said that by doing this, all =
of our existing dialup customers can keep their Primary and Secondary =
DNS DUN settings unchanged, since our nameservers will still be =
associated with the old addresses. As new customers sign up, we would =
have them configure their DUN settings with the new numbers, but we =
wouldn't have to spend the hours of technical support helping our =
existing customers change their DUN settings. =20
Does this plan sound plausible to anyone? I'm wondering if there will =
be any routing issues on the Internet at large if only our dialup =
customers use the old DNS numbers. If not, it seems like maybe this is =
the right approach to take (in addition to the other steps recommended =
by Terry and others, of course). =20
=20
-----Original Message-----
From: Terry Bomersbach <terryb@the-cia.net>
To: ntisp@iea-software.com <ntisp@iea-software.com>
Date: Monday, July 05, 1999 8:43 AM
Subject: Re: [NTISP] Advice on Changing Backbone Providers
Sprint is a tad slower but always consistent. We found that during the
changing of the guard at MCI, they were constantly loosing routers so we =
had
to fall back to Sprint for our upstream.
I'd recommend running dual systems for about two weeks and slowly moving
traffic over to the new IPs until only your Mail, FTP, WWW, Primary and
Secondary DNS servers are the only machines on the old subnets. Then =
just
kill the old subnet and move on without a hitch.
Please note that if you have colocates, they will need to make sure that
they update their records with internic also.
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart