 |  |
At 2:51 PM -0400 6/12/03, m i l e s wrote:
Re: IP Renumbering Nightmare Coming....
From: Men & Mice Support
Date: Thursday, June 12, 2003
Time: 12:40:42 pm
>Hi,
>
>My upstream provider is renumbering their IPs.
>
>EEEEEEEEK!
>
>What Im worried about or concerned about is changing
>over my dns to the new IPs. Obviously there's going to
>be some issues with mail and web services...I know that
>Im going to lose some traffic while the change over happens,
>but from a DNS stand point, are there any gotcha's I should
>know about ahead of time ?
Make sure none of your hostnames other than your actual DNS servers
are registered as hosts with the registrars.
For example, suppose you at one point used "www.magicmiles.com" as a
DNS server, but no longer do so. The record of that might still be in
the gTLD servers, using the old address. This can cause all kinds of
fun after you move - before you move, you'd never notice, because the
name resolves correctly.
>Here's my thinking, that I'll have to go in and change the
>IPs in the entire table, I know that.
AppleScript can help with that. We included some nifty AppleScripts,
including one designed to do exactly this - find one IP address and
replace it with another one, across all zones.
>That obviously has to
>change. I'll need to go re-register my nameserver with
>my registrar with its new IP address...Anywhere where
>Ive got code that has the OLD IP addresses has to change,
>email server, webserver, list server, all have to change...
>obviously the machines have to change their IPs.
>
>Anywhere else ? Hmmm my DNS is running on an
>8600 on Mac OS 8.6! Its QDNS v3.5.3. I know that
>OS 9 can handle listening on multiple IPs, but Im
>not so certain about OS 8.6. Anyone want to answer
>that one ?
The operating system can (starting with 8.1). QuickDNS Server, however, cannot.
>Second question...
>
>Is it wise that I should run a secondary DNS (my upstream
>provider is already running secondary for me) but is this
>a case where Im thinking that I might have to run a secondary
>DNS for a lil while on the same machine, or just make new
>entries in the DNS table for the new IP addresses, so that its
>listening on both sets of IPs ?
Set the refresh and retry values in all of your zones to a lower
value, such as 5 minutes (300 seconds). Also change the default TTLs
to a low value (again, 5 minutes is good).
Then get an off-site slave server. One whose IP address isn't going
to change. Update all your domains' registration records to reflect
the new server.
Then go about making your changes, secure in the knowledge that you
won't suffer a DNS outage. Whenever a machine goes from old address
to new address, change the A record(s). The rest of the world will
find out within 10 minutes.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy
Messages In This Thread:
Return to Digital Point Solutions' Home Page
| home | |
| products | |
| services | |
| support | |
| email lists |
| optigold isp | |
| optigold isp news | |
| home inspection | |
| inspectrix | |
| java companion | |
| oracle | |
| quickdns pro | |
| search engine | |
| veterinary |
| tips | |
| employees | |
| free tools | |
| portfolio | |
| jobs | |
| contact |
888/4-DPOINTSupport:
858/452-3696