Date: Wed, 22 Apr 1998 11:02:35 +0200 (MET DST) From: Ugo Paternostro <paterno@dsi.UNIFI.IT> To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: DNS Cache+MX+SendMail = Host not found... Message-ID: <XFMail.980422110235.paterno@dsi.unifi.it> In-Reply-To: <Pine.BSF.3.96.980421135445.4368D-100000@gdi.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21-Apr-98 Doug White wrote about "Re: DNS Cache+MX+SendMail = Host not found...": > It's commonly used for pointing hosts inside a firewall to the bastion > host for real transmission, and the bastion host firewall method is what > you're using it looks like. Yes: it is not a true firewall, just a PPP dialup connection. > This is starting to get into the sendmail voodoo magic which I know very > little about. Me too :-) Don't ask me how I was able to build a new mailer... ;-) >> Well, it seems to do that: the mail bounces back to me with a "host not >> found" error referring to anotherplace.some.domain (the MX record). > > That would make sense. It depends on how anotherplace.some.domain dies, I Hey, wait: anotherplace.some.domain lives! It's me that commit suicide ;-) To explain better, I have a dialup connection and the problem happens when I'm not connected. BTW, as time goes by, I understand that my original question wasn't that clear... :-) > would guess. Can you send mail directly to anotherplace.some.domain, for > instance? Yes, when my link is up ;-) If I try to send a mail to foo@anotherplace.some.domain when I'm not connected to my ISP, sendmail simply queues the mail (because of a failed DNS search, or a "no route to host" error if the name was cached). The problem appears only when sendmail know that the host you're sending mail to has an MX, but it (sendmail) doesn't know anything about the MX. This may happen when I drop the PPP link because my DNS caches only the MX record, but not the address the MX is pointing to (maybe it caches both, but the latter expires). Currently I have three solution: a. wait for the MX record in the NameServer cache to expire (loooooongggg...) b. restart the name server (but I loose cache contents) c. pester Doug White :-) > Doug White | University of Oregon Bye, UP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980422110235.paterno>