From owner-freebsd-questions@FreeBSD.ORG Wed Aug 31 16:25:29 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 B95C216A41F for ; Wed, 31 Aug 2005 16:25:29 +0000 (GMT) (envelope-from nalists@scls.lib.wi.us) Received: from mail.scls.lib.wi.us (mail.scls.lib.wi.us [198.150.40.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6117643D46 for ; Wed, 31 Aug 2005 16:25:29 +0000 (GMT) (envelope-from nalists@scls.lib.wi.us) Received: from [172.26.2.238] ([172.26.2.238]) by mail.scls.lib.wi.us (8.12.9p2/8.12.9) with ESMTP id j7VGPSG1042226; Wed, 31 Aug 2005 11:25:28 -0500 (CDT) (envelope-from nalists@scls.lib.wi.us) Message-ID: <4315D92D.9020400@scls.lib.wi.us> Date: Wed, 31 Aug 2005 11:22:05 -0500 From: Greg Barniskis User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jerod Prothe References: <4315C67B.9020907@usd217.org> <4315CF0E.2020707@scls.lib.wi.us> <4315D177.5040900@usd217.org> <4315D3CD.9090807@meijome.net> In-Reply-To: <4315D3CD.9090807@meijome.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org 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:25:29 -0000 Norberto Meijome wrote: > Jerod Prothe wrote: >> >> CNAME to galley? That's a good idea. > > this will only affect those who have an updated record of your zone and > can see that new record. For those that still think that MX is otto on > it's real(old) IP, the CNAME wont help them a bit. Assigning otto's > public IP to galley will fix this problem. Doh! /me thwacks self with clue stick... so obvious, especially when we did exactly that on our last mail server replacement, in order to avoid this very problem. > Also, you may want to make triple sure the serial of your zone gets > updated with every change...else downstream DNS servers wont necessarily > pickup the changes. >> I changed it and reduced the expire time to 10d (I got it out of the >> Lehey Complete FreeBSD book). I wonder why it is that Australia has >> updated but a US State has not? 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. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348