From owner-freebsd-stable@FreeBSD.ORG  Thu Oct 26 21:06:13 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4B09416A40F
	for <freebsd-stable@freebsd.org>; Thu, 26 Oct 2006 21:06:13 +0000 (UTC)
	(envelope-from VIVEK@KHERA.ORG)
Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 08D3B43D49
	for <freebsd-stable@freebsd.org>; Thu, 26 Oct 2006 21:06:12 +0000 (GMT)
	(envelope-from VIVEK@KHERA.ORG)
Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103])
	by yertle.kcilink.com (Postfix) with ESMTP id 49CE5B822;
	Thu, 26 Oct 2006 17:06:12 -0400 (EDT)
In-Reply-To: <s540beef.065@bat-gwpo.ccsf.edu>
References: <s540beef.065@bat-gwpo.ccsf.edu>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B10228D3-FDD2-40F3-89BF-69062ABB25B8@KHERA.ORG>
Content-Transfer-Encoding: 7bit
From: Vivek Khera <VIVEK@KHERA.ORG>
Date: Thu, 26 Oct 2006 17:06:11 -0400
To: "Glen Van Lehn" <gvanlehn@ccsf.edu>
X-Mailer: Apple Mail (2.752.2)
Cc: freebsd-stable@freebsd.org
Subject: Re: whither cvsup11?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Oct 2006 21:06:13 -0000

On Oct 26, 2006, at 4:57 PM, Glen Van Lehn wrote:

> looks like they fixed it very recently.

one of the uunet/verizon guys posted that they've reconfigured the  
zone so it is served primarily from the main NS servers rather than  
the "beast" server, which appears down.

That was about 1.5 hours ago, so propagation should have worked its  
magic by now.