Date: Thu, 20 Jan 2005 17:03:05 -0500 From: "Niy" <Niy@extacy.homeip.net> To: "'Joe Kraft'" <hishadow@netcabo.pt> Cc: questions@freebsd.org Subject: RE: Sendmail: host name lookup failure Message-ID: <20050120220311.CB53A43D49@mx1.FreeBSD.org> In-Reply-To: <41F0228B.7020108@netcabo.pt>
next in thread | previous in thread | raw e-mail | index | archive | help
-----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Joe Kraft Sent: Thursday, January 20, 2005 4:29 PM To: freebsd-questions@freebsd.org Subject: Re: Sendmail: host name lookup failure Paul A. Hoadley wrote: > On Mon, Dec 20, 2004 at 10:54:42PM +1030, Paul A. Hoadley wrote: > > I am told it's running Windows 2000 DNS Server. Presumably that's > Microsoft's own DNS implementation built into Windows 2000. > > (By 'sometimes' I don't mean it's non-deterministic. Every time > sendmail asks for the AAAA record of an unqualified hostname, the > nameserver responds with SERVFAIL.) > > The consequence of this is that sendmail repeatedly defers delivery > until the mail expires. > > >>Curiously, sendmail's WorkAroundBrokenAAAA option did not help, and I >>don't know why. Daryl Tester suggested using a mailertable entry, and >>this worked. > > > I still don't know why WorkAroundBrokenAAAA isn't working in this > case. > > > I'm running into the exact same problem. My dns is a Win2k server, the mail server is FBSD5.3 called kara.home.local. The dig to kara.home.local >> >works fine, but to kara fails. > >have you found out any more about why it's not working? I'm also curious about the entry in mailertable because my feeble attempt didn't work. > >I appreciate any info you can pass on. > >Thanks, >Joe. > >_______________________________________________ >freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" Just a quick thought, I had a similar problem on my LAN. I set up /etc/hosts files, and that did the trick for me. I could then dig both the fqdn and the host name just fine. For example, for a machine on my internal lan with the fqdn of empathy.whatever.net, I set up on the machines that had to reach it: 192.168.0.10 empathy empathy In the /etc/hosts file. Man hosts for more info. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050120220311.CB53A43D49>