From owner-freebsd-isp Wed Oct 25 8:48:18 2000 Delivered-To: freebsd-isp@freebsd.org Received: from euclid.cs.niu.edu (euclid.cs.niu.edu [131.156.145.14]) by hub.freebsd.org (Postfix) with ESMTP id 1C99337B479 for ; Wed, 25 Oct 2000 08:48:16 -0700 (PDT) Received: from localhost (rickert@localhost [127.0.0.1]) by euclid.cs.niu.edu (8.12.0.PreAlpha2/8.12.0.PreAlpha2) with ESMTP id e9PFmCK13078; Wed, 25 Oct 2000 10:48:12 -0500 (CDT) X-Mailer: exmh version 2.1.2 06/08/2000 To: "Dave Wilson" Cc: sendmail-questions@sendmail.org, freebsd-isp@FreeBSD.ORG Reply-To: sendmail-questions@sendmail.org Subject: Re: Cached MX References: <00c001c03e42$9678b2b0$112821c4@sai.co.za> In-Reply-To: Message from "Dave Wilson" of "Wed, 25 Oct 2000 07:15:23 +0200." <00c001c03e42$9678b2b0$112821c4@sai.co.za> Date: Wed, 25 Oct 2000 10:48:12 -0500 Message-ID: <13075.972488892@euclid.cs.niu.edu> From: Neil W Rickert Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Dave Wilson" wrote: >Does sendmail cache MX entries ? At most, for the life of a single process during a queue run. >I have updated an MX record for mydomain.com on our DNS server, if I do a >"dig MX mydomain.com" it shows the new updated MX, but when I use sendmail >to try and send to mydomain.com sendmail still seems to be trying to send it >back to the old host (MX record). If that is due to MX caching, then the caching is being done by your DNS nameserver. Check '/etc/resolv.conf', then check each of the nameservers listed dig @ip-of-nameserver mydomain.com mx Also make sure that you are not using a mailertable or other special configuration to bypass the MX record. -NWR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message