From owner-freebsd-questions@FreeBSD.ORG Wed Aug 31 16:43:33 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 3E25216A41F for ; Wed, 31 Aug 2005 16:43:33 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF9D643D45 for ; Wed, 31 Aug 2005 16:43:32 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 10456 invoked from network); 1 Sep 2005 02:43:32 +1000 Received: from 203-217-79-78.dyn.iinet.net.au (HELO ?192.168.13.3?) (203.217.79.78) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Sep 2005 02:43:32 +1000 Message-ID: <4315DE30.3040909@meijome.net> Date: Thu, 01 Sep 2005 02:43:28 +1000 From: Norberto Meijome User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4315C67B.9020907@usd217.org> <4315CF0E.2020707@scls.lib.wi.us> <4315D177.5040900@usd217.org> <4315D3CD.9090807@meijome.net> <4315D92D.9020400@scls.lib.wi.us> In-Reply-To: <4315D92D.9020400@scls.lib.wi.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: mail malady - dns/postfix X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 16:43:33 -0000 Greg Barniskis wrote: > Hard to say, but as far as a management discussion goes, it is clear > that this problem has really nothing to do with your selection of > FreeBSD as DNS/mail host, and (barring better failsafe procedures like > IP number migration) would have occurred regardless of the OS chosen. > The problem as such is 3rd party systems you can't control. > indeed. my first rule of 'planned' DNS changes: lower refresh to minimum acceptable. then when I'm sure everything works, up it to my defaults. And , btw, if you hear of those DNS hosters that tell you they have "instant propagation" , make sure you read the very very small footprint that says "within our network". i.e., DNS is a game where all DNS servers play along...or not ;) b