 |  |
At 10:55 AM +0000 1/14/2000, Mark Palmer, Pageworks wrote:
Re: Changing ISP, updating DNS
From: Men & Mice Support
Date: Saturday, January 15, 2000
Time: 12:53:00 am
>I think I got it backwards in my original post. Tell me if this
>thinking is correct.
>
>1. I change the TCP/IP control panels on each of web, mail and DNS
>to the new IP numbers
>2. I make an additional Mac IP Multi-homing entry using the OLD IP
>number for that machine.
>3. I amend all my domains in QDNS to the new IP range.
>4. I update my records at Nominet (the UK naming authority), I think
>this only really effects which host name they look for for
>secondary. Please tell me if I'm wrong!
>
>Then presumably what is now stale data within the DNS as a whole
>will find a host on the old number, and as the DNS updates itself,
>QDNS will respond with the new data as time clicks on. Am I correct
>in thinking there is no need for me to run a second copy of QDNS
>using the OLD IP number, becuase some other DNS server is going to
>resolve those numbers temporarily.
Bad order of operation. What you've outlined would take down at least your DNS services, and possibly others, until everything is updated.
I've taken a look at your DNS, and I see a better way to do this, based on the fact that you already have two DNS server of your own (plus one at your old [?] provider) and the fact that none of your services appear to be on the same machine. In other words, ns1, ns2, mail, and www (in the pageworks.co.uk domain) are all different machines.
1) Move ns2.pageworks.co.uk to its new address - change the address in TCP/IP.
2) Ask Nominet (who I take it is the domain registrar of commercial domains in the UK) to change your registration records for pageworks.co.uk, which should have the effect of updating the rest of your domains as well. Your new records should point to both ns1 and ns2 (and dns1.red.net, if you're going to continue using this server), but use only the new addresses. Don't worry about the fact that the addresses aren't all yet in use; ns2 will take the load by itself.
3) Add secondary addresses to all your other servers. Don't bother with your QuickDNS Pro servers, since they won't see the extra addresses anyway. (Make sure all your other services support multiple addresses - I'm not sure about CommuniGate.) Configure all these services to use their new extra addresses. (You can either put the new addresses in Secondary Addresses, or switch them; it doesn't matter.)
4) Now start changing your DNS records for all your domains to point to the new addresses. Since all services are in place on both subnets, there will be no disruption of services. When all is changed, reboot your secondary server. Ask your provider to reboot dns1.red.net, too.
5) Wait. You'll need to wait at least (TTL + TTL of delegation records) seconds from the time the delegation records are changed, or (TTL) seconds from the time the DNS records are changed, whichever is longer. Currently, your delegation records have a 4 hour TTL, and your own records have a 24 hour TTL; you can turn down your TTL beforehand to minimize this, but then remember to wait for the new TTL to be noticed - a wait of at least (old TTL) seconds.
6) Take down all your old addresses. Move ns1 to its new address. If you're not going to be using red.net's servers anymore, ask them to remove their settings for your domains (both DNS and mail).
>If I happily start editing each domains details in QDNS what can I
>expect to happen and when? How long before the rest of the world is
>up to date? I'm using whatever default value of TTL QDNS shipped
>with. Can I drop this value now to a couple of minutes, without
>changing the IP numbers, allow this to propogate around the world
>and then change the IP numbers and bump the TTL back, hoping things
>will update faster.
Dropping it to a couple of minutes is extreme, as this will cause extra DNS traffic on your lan. 1 hour (3600) isn't out of line, though.
>Are there certain times of the day when root servers update
>themselves, if so can I take advantage of this?
None of your information on the root servers needs to be changed, except possibly to remove your old ISP's DNS server. They refer to your DNS servers by name only, since you're in the UK domain.
Unfortunately, you can't time the root servers anyway, since they have to be modified by the domain registrar (probably Network Solutions), and the first person who can accurately predict when NetSol will do anything could probably make a fortune.
The root servers are updated once every 48 hours. I don't recall when, exactly, though.
____________________________________________________________________
Chris Buxton cbuxton@menandmice.com
Men & Mice http://www.menandmice.com
Makers of: QuickDNS Pro
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