Date: Thu, 16 Dec 2004 11:32:58 +1030 From: "Paul A. Hoadley" <paulh@logicsquad.net> To: freebsd-questions@freebsd.org Subject: Sendmail: host name lookup failure Message-ID: <20041216010258.GC93695@grover.logicsquad.net>
next in thread | raw e-mail | index | archive | help
--CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I have just upgraded a machine from 5.2.1 to 5.3, and I think I _may_ have stomped on something in /etc/mail during mergemaster. The symptom is this: mail to other machines on the LAN worked yesterday, and is broken after the upgrade. Mail to the wider Internet continues to work. I have a series of mails in the queue, failing on delivery attempts like this: Dec 16 11:19:08 bert sendmail[1043]: iBF403Wb004664: to=3D<marc@coremedicalsolutions.com>,<paul@coremedicalsolutions.com>,<rohan= @coremedicalsolutions.com>, ctladdr=3D<paulh@bert.coremedicalsolutions.com> (1001/1001), delay=3D20:49:05, xdelay=3D00:00:00, mailer=3Desmtp, pri=3D4770661, relay=3Dtsb.coremedicalsolutions.com., dsn=3D4.0.0, stat=3DDeferred: Name server: tsb.coremedicalsolutions.com.: host name lookup failure Running sendmail on the queue in verbose mode gives this: Running /var/spool/mqueue/iBG097Eq000666 (sequence 1 of 118) <paul@coremedicalsolutions.com>... Connecting to tsb.coremedicalsolutions.com. via esmtp... [long pause] <paul@coremedicalsolutions.com>... Deferred: Name server: tsb.coremedicalsolutions.com.: host name lookup failure Running /var/spool/mqueue/iBFNpkMQ052047 (sequence 2 of 118) <paul@coremedicalsolutions.com>... Deferred: Name server: tsb.coremedicalsolutions.com.: host name lookup failure [...] There are numerous hits from Google on very similar issues, but almost all the solutions point at DNS problems. If there is a local DNS issue, I can't find it. > dig coremedicalsolutions.com. mx [...] coremedicalsolutions.com. 3600 IN MX 10 tsb.coremedicalsolutions= .com. [...] tsb.coremedicalsolutions.com. 900 IN A 192.168.10.69 > dig -x 192.168.10.69 [...] 69.10.168.192.in-addr.arpa. 900 IN PTR tsb.coremedicalsolutions.co= m. > dig bert.coremedicalsolutions.com. [...] bert.coremedicalsolutions.com. 900 IN A 192.168.10.78 > dig -x 192.168.10.78 [...] 78.10.168.192.in-addr.arpa. 900 IN PTR bert.coremedicalsolutions.c= om. That is, both the originating machine (bert) and the receiver (tsb) have forward and backward DNS entries. Can anyone suggest the next step in diagnosing this? --=20 Paul. w http://logicsquad.net/ h http://paul.hoadley.name/ --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBwN7B730Z/jysbzIRAmLsAJ9LgteC2Zp7dENSI6V5cQWWoNmtKgCcCWEu F48N6aVOz3z6EAoFQgoheTE= =kZbF -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041216010258.GC93695>