No Meeting

[Stephen Burke]

This all sounds just a bit TOO fascinating to one, like me, who has 
never performed such digital feats before. It also sounds like a fair 
bit of actual work, both digitally and physically, performing the whole 
move, migration, etc. I would be happy to assist in whatever way I can 
with both physical and digital maneuvers, just to observe the whole 
process and learn a thing or two along the way.

My schedule is unpleasantly free at the moment, so I could be available 
whenever (coming from Amherst),  but the last two years of night classes 
have left me on a sort of vampire-like sleeping rythm, so evenings are 
best if you want me to be awake enough not to drop any computers. ;-)

Please let me know if I can be of assistance in the move.

Thanks,
S.

Dave Andruczyk wrote:

>--- Robert Meyer <meyer_rm at yahoo.com> wrote:
>
>  
>
>>Sorry for the late notice.  We no longer can use the building at 100 S.
>>Elmwood
>>for meetings.  I found out that the NYCLU is in the process of moving to a
>>new
>>location.  The heat has already been turned off at the site on Elmwood and it
>>would be quite uncomforatble, anyway.
>>
>>I don't know where the new office is going to be but I've been told that it's
>>much larger than the old office.  We will probably be allowed to use the new
>>site for meetings when it's set up.
>>
>>I am not going to enjoy moving all of the equipment that is there to the new
>>location.  Does anybody know if there is a way to get Verision to let us keep
>>our old addresses when it moves?  If I can't do that, I'm going to have fun
>>because our primary and secondary name servers are on the current network and
>>changing them all is going to be a stunning pain in the butt.
>>
>>    
>>
>
>Well if they can't give you the same addresses when you move, follow a
>procedure like the one below and it'll minimize (even eliminate) DNS outages if
>you do the steps at the right times.
>
>About 4-7 days before moving:
>At the very least set the DNS TTL's for all the records (time to live) to VERY
>low levels (20 minutes, 1200 seconds) and have at least One DNS server (the
>secondary) moved to a different network now and switched to the primary DNS
>server(update the registrar info to set the external DNS server as the PRIMARY
>and the one at the place being being shutdown as the secondary, Edit the DNS
>servers configs so it knows who is master and who is the slave).  
>Make sure the external primary DNS is working properly and the internal
>secondary is geting changes from the primary  It can take up to 48 hours for
>the whois info to change and outside DNS servers to recognize that the primary
>DNS server is a different one.
>
>On the day before the move update the registrar's info on the secondary DNS
>server(the one remaining to be moved) to it's new network address that takes
>effect on the following day) 
>
>On the day of the move, turn the TTL's down to about 1 minute(60 seconds)), get
>everything moved and update all DNS records to use the new addresses(this gets
>done on the primary which is at an external location, make sure you update the
>secondary's address on the primary, and on the secondary make sure you set the
>"master" address correctly).  
>
>Now at this point you'll have the primary DNS server sitting someplace remote,
>and the secondary will be at the new office.  Go back and update the registrar
>into to reverse the DNS roles back again (so that the one at the office is
>primary and the one outisde is secondary, turn the TTL's up to around 30
>minutes, *(update the DNS server configs again so the internal one is maser and
>the other is slave))  
>
>Wait a day or two to make sure it takes effect, then move the "outside" one to
>the new office and update the registration one last time to give it it's new
>address.  Make sure it works then turn the TTL's back up to 86400 (one day) to
>bring the DNS load back down to normal levels.
>
>
>
>=====
>Dave J. Andruczyk
>
>
>		
>__________________________________ 
>Do you Yahoo!? 
>Yahoo! Mail - Find what you need with new enhanced search.
>http://info.mail.yahoo.com/mail_250
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.nflug.org/pipermail/nflug/attachments/20041219/45655f1a/attachment-0001.html