From owner-freebsd-questions Tue Jan 21 14:27: 9 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0D6437B405 for ; Tue, 21 Jan 2003 14:27:07 -0800 (PST) Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58F5143F13 for ; Tue, 21 Jan 2003 14:27:07 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kciLink.com (onceler.kciLink.com [216.194.193.106]) by yertle.kciLink.com (Postfix) with ESMTP id 33364217B3 for ; Tue, 21 Jan 2003 17:27:01 -0500 (EST) Received: by onceler.kciLink.com (Postfix, from userid 100) id 06FA63D62; Tue, 21 Jan 2003 17:27:00 -0500 (EST) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Vivek Khera To: freebsd-questions@freebsd.org Subject: Re: Root Servers - Nameserver Update. Newsgroups: ml.freebsd.questions References: <000501c2c0d4$5c74e680$6501a8c0@grant> X-Trace: lorax.kciLink.com 1043184431 64931 216.194.193.106 (21 Jan 2003 21:27:11 GMT) X-Complaints-To: daemon@kciLink.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "GP" == Grant Peel writes: GP> 1) Does anyone KNOW when the root servers update DNS for hosts (NS's)? GP> 2) We were planning to change the DNS about 11:00 P.M. this Saturday, Taking This requires advanced planning on the order of the TTLs of your domain records. First thing is to update your zones to cut the TTL down to a few hours or even minutes. You need to do this so that the current TTL expires *before* your intended move. If your current TTL is 7 days, you're too late ;-( Just before moving, issue the NS record updates with your registrar. Hopefully you use a registrar that lets you do this dynamically via the web. It usually won't take effect for at least a day as the top-level zone files are not updated but once per day, I believe. If you have secondary DNS servers that are outside your network that is moving (this is a prime example of why this is recommended), be sure to update your DNS server and have the secondary fetch a copy of the new zone file. Then move the network, bring it all up again, and you should be good to go. If your TTL is shorter than the move time only some *really* broken remote sites won't notice in time. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message