Sendmail: host name lookup failure

[Paul A. Hoadley]

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=<marc at coremedicalsolutions.com>,<paul at coremedicalsolutions.com>,<rohan at coremedicalsolutions.com>,
ctladdr=<paulh at bert.coremedicalsolutions.com> (1001/1001),
delay=20:49:05, xdelay=00:00:00, mailer=esmtp, pri=4770661,
relay=tsb.coremedicalsolutions.com., dsn=4.0.0, stat=Deferred: 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 at coremedicalsolutions.com>... Connecting to
tsb.coremedicalsolutions.com. via esmtp...

[long pause]

<paul at coremedicalsolutions.com>... Deferred: Name server:
tsb.coremedicalsolutions.com.: host name lookup failure

Running /var/spool/mqueue/iBFNpkMQ052047 (sequence 2 of 118)
<paul at 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.com.

> 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.com.

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?


-- 
Paul.

w  http://logicsquad.net/
h  http://paul.hoadley.name/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20041216/de8de9a9/attachment.bin