|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
May the source be with you, but remember the KISS principle ;-)
Bigger doesn't imply better. Bigger often is a sign of obesity, of lost control, of overcomplexity, of cancerous cells
Re: Changing ISP, updating DNS
Re: Changing ISP, updating DNS
Date: Friday, March 10, 2000
Time: 4:01:00 am
I'm about to switch ISPs. The old isp's line is up and the new isp's line is also up. I search menandmice.com site for a howto on changing but didn't find one...
From reading this thread of messages I've come up with this perliminary plan to switch services from the old addresses to to the new addresses.
1. Change the ttl's for each domain down to 1 hour (3600) on the primary name server. (which I did about an 6:30pm pst...)
2. I'll move the secondary dns server to the new network sometime in the next day or too...
3. Update all the primary records to reflect the new secondary server...
4. Move the least used server (or service) to the new network connection and update the primary dns pointing to it's new home.
5. Repeat 4 for each server.
6. When the last server on the old network is the primary DNS then I'll setup a temporary dns server to act as a primary on the new network. Update Internic records. And wait...
7. Once primary dns changes are reflected by Interic. Then shut down the old network. move the old primary dns to the new network to replace the temporary...
So. is this a reasonable course of action to pursue? Any pitfalls or
variations that make the switch over easier/better...
Thanks for any advice.
From: Men & Mice Support
Date: Saturday, January 15, 2000
Time: 12:53:00 am
At 10:55 AM +0000 1/14/2000, Mark Palmer, Pageworks wrote: 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 firstname.lastname@example.org
Men & Mice http://www.menandmice.com
Makers of: QuickDNS Pro
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2018 by Dr. Nikolai Bezroukov. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Created May 16, 1996; Last modified: September 12, 2017