 |  |
Re: Changing ISP, updating DNS
From: Mark Palmer, Pageworks
Date: Friday, January 14, 2000
Time: 10:55:00 am
On Fri, Jan 14, 2000, 10:13:12 AM GMT Men & Mice Support wrote:
Thanks for you reply, more questions!
>>It did occur to me that I could give the web, mail and DNS servers
>>each an additional IP number (using Apples IP Multi-homing) from my
>>new range allocated to me. Thus during the period that the domain
>>name system is updating itself a domain name that resolves to
>>100.100.100.100 or the new IP 200.200.200.200 would find a host.
>>
>>Would this work or is it a daft idea.
>>
>>Oh BTW, I will still have the old leased line and its router still
>>in place when the new stuff is up and running.
>QuickDNS Pro won't respond on any address besides the one configured
>in TCP/IP. So you'd have to set up one additional DNS server for each
>one you currently have, on the old addresses. (We won't mind a
>temporary arrangement like that - no need to buy additional copies
>just for this.)
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.
>Alternatively, if the router on your old lease line supports in-bound
>NAT, you could change all your addresses, then enable that feature to
>map incoming requests to the correct servers, using the original
>destination IP to determine the new destination IP.
>
>If your router doesn't support this, you could probably set it up on
>a spare machine using IPNetRouter from Sustainable Softworks
><http://www.sustworks.com/>. You might even be able to run IPNR on
>one of your servers without disrupting its other tasks (try it before
>depending on that).
>
My old router is a Cisco 1601, but it came pre-configured by the ISP and I've never touched it. I had a poke around the manuals and it looks horrible. I wouldn't have a clue whether it support NAT and if it did how to configure it. I'll soon have a router I paid a fortune for doing nothing because the new ISP supplies a free 2501 :-(
>>I'm changing ISP shortly. Can you point me at any information on how
>>best to update my DNS to ensure the minimum loss of service to
>>clients. Any tips or tricks.
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.
Are there certain times of the day when root servers update themselves, if so can I take advantage of this?
Sorry for all the questions, I want to amke this as smooth as possible.
Regards
Mark Palmer, Pageworks
T: 01902 620500 F: 01902 620440
E: mark@pageworks.co.uk W: www.pageworks.co.uk
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