>X-AV-Checked: Sat Mar 24 23:56:29 2007 virusgate.meiway.com >X-Original-To: [EMAIL PROTECTED] >Delivered-To: [EMAIL PROTECTED] >Date: Sat, 24 Mar 2007 23:56:28 +0100 (CET) >From: Ecartis <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >X-ecartis-antiloop: mgw2.meiway.com >Subject: imgate: [EMAIL PROTECTED] post needs approval >X-RCPT-TO: <[EMAIL PROTECTED]> > >This message was received for a list you are a moderator on, and >was marked for moderation due to the following reason: >Non-member submission to closed-post list. > >To approve this message and have it go out on the list, forward this to >[EMAIL PROTECTED] > >If you wish to decline the post, change the 'apppost' below to 'delpost'. >If you wish to edit the post, change it to 'modpost' and edit the message >as needed - not all mail programs will work with modpost. > >DO NOT DELETE THE FOLLOWING LINE. Ecartis needs it. >// apppost 4605AC9C:10D93.1:vztngr > > >From [EMAIL PROTECTED] Sat Mar 24 23:56:28 2007 >Return-Path: <[EMAIL PROTECTED]> >X-Original-To: [email protected] >Delivered-To: [email protected] >Received: from omx4.sandiegort.com (omx4.sandiegort.com [69.43.139.66]) > by mgw2.meiway.com (Postfix) with ESMTP id A8B3C47186C > for <[email protected]>; Sat, 24 Mar 2007 23:56:28 +0100 (CET) >Received: from cs2.sandiegort.com (cs2.sandiegort.com [69.43.139.62]) > by omx4.sandiegort.com (Postfix) with ESMTP id 83F9E68614 > for <[email protected]>; Sat, 24 Mar 2007 15:56:18 -0700 (PDT) >X-Virus-Scanned: amavisd-new at sandiegort.com >Received: from smtp1.icsandiego.com (smtp1.icsandiego.com [69.43.139.33]) > by cs2.sandiegort.com (Postfix) with ESMTP id 901344AC18 > for <[email protected]>; Sat, 24 Mar 2007 15:56:17 -0700 (PDT) >Received: from mikeblap (ip68-7-207-60.sd.sd.cox.net [68.7.207.60]) > by smtp1.icsandiego.com (Postfix) with ESMTP id 7E91A19E019 > for <[email protected]>; Sat, 24 Mar 2007 15:56:17 -0700 (PDT) >Reply-To: <[EMAIL PROTECTED]> >From: "Mike Barnett" <[EMAIL PROTECTED]> >To: <[email protected]> >References: <[EMAIL PROTECTED]> ><[EMAIL PROTECTED]> ><[EMAIL PROTECTED]> >Subject: RE: [IMGate] Re: how long for host records to arrive in TLD-servers? >Date: Sat, 24 Mar 2007 15:56:17 -0700 >Message-ID: <[EMAIL PROTECTED]> >MIME-Version: 1.0 >Content-type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 8bit >X-Mailer: Microsoft Office Outlook 11 >thread-index: AcduYLB5ii6BKv13S2inGkmKTa2o+gAAgh+A >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 >In-Reply-To: <[EMAIL PROTECTED]> > >We register thousands of domains (as well as make many changes to existing >domains) and I have never seen it take longer than a day, in fact we promise >2 days to customers.. > > >Mike > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >On Behalf Of Len Conrad >Sent: Saturday, March 24, 2007 3:04 PM >To: [email protected] >Subject: [IMGate] Re: how long for host records to arrive in TLD-servers? > > > >I think it can take up to 48 hours with some registrars. Others like > >Dotster update more often (hourly) although I think the root servers > >only update 1-2 times a day anyway. > >Nit: we're not talking about the *.root-servers.net but about the >*.gTLD-servers.net, which are the .com domain parents. A common >misstatement fostered the dnsreports. > >We're nearly at 48 hours after the whois database was updated without the >updating of the *.gTLD-servers.net. Maybe by Monday. > >Len > > > > > > >// eompost 4605AC9C:10D93.1:vztngr
