From: "greg scott" <x-x@comcast.net>
To: 9fans@cse.psu.edu
Subject: [9fans] smtp dns failure: mx lookup
Date: Mon, 2 Jan 2006 19:50:24 -0600 [thread overview]
Message-ID: <bde13d79d0a3adcb1545e5484908131f@comcast.net> (raw)
trying to send mail (Post tag in acme mail) results in
this /sys/log/smtp.fail entry
dns: dns failure (net!smtp.comcast.net)
the logs below from /sys/log/dns indicate that sending
mail results in an MX type query (smtp.comcast.net mx)
which fails with "dns failure 25".
as a workaround to this send failure:
if "ip/ping smtp.comcast.net" is run first, mail does
get sent immediately, with no smtp.fail log.
this is good for 10 minutes, after which a new ping is
needed in order for new mail to be sent.
failed ("stuck") mail is sent out too after a successful send
due to the ping.
ip/ping results in an IP type query (smtp.comcast.net ip) which
succeeds, with dns returning ip addresses for smtp.comcast.net
192.168.0.1 is a router/firewall that forwards dns lookup requests
to comcast dns servers.
any ideas how to fix this?
/sys/log/dns details:
sending mail (acme Post tag) results in this mx query:
192.168.0.104 Jan 2 21:18:44 Twalk tag 15 fid 116 newfid 318 nwname 1 0:dns
192.168.0.104 Jan 2 21:18:44 Rwalk tag 15 nwqid 1 0:(0000000000000001 72 ) 22
192.168.0.104 Jan 2 21:18:44 Topen tag 15 fid 318 mode 2
192.168.0.104 Jan 2 21:18:44 Ropen tag 15 qid (0000000000000001 72 ) iounit 0 24
192.168.0.104 Jan 2 21:18:44 Twrite tag 15 fid 318 offset 0 count 19 'smtp.comcast.net mx'
192.168.0.104 Jan 2 21:18:44 dnresolve1 smtp.comcast.net 15 1
192.168.0.104 Jan 2 21:18:44 641.1: sending to 192.168.0.1/local#dns#server0 smtp.comcast.net mx
192.168.0.104 Jan 2 21:18:44 641: rcvd 192.168.0.1 flags: rd ra
192.168.0.104 Jan 2 21:18:44 641: rcvd 192.168.0.1 qd smtp.comcast.net
192.168.0.104 Jan 2 21:18:44 641: rcvd 192.168.0.1 ns comcast.net soa dns01.jdc01.pa.comcast.net dnsadmin.comcast.net 1428 900 180 604800 3600
192.168.0.104 Jan 2 21:18:44 dnresolve1 smtp.comcast.net 5 1
192.168.0.104 Jan 2 21:18:44 641.1: sending to 192.168.0.1/local#dns#server0 smtp.comcast.net cname
192.168.0.104 Jan 2 21:18:44 641: rcvd 192.168.0.1 flags: rd ra
192.168.0.104 Jan 2 21:18:44 641: rcvd 192.168.0.1 qd smtp.comcast.net
192.168.0.104 Jan 2 21:18:44 641: rcvd 192.168.0.1 ns comcast.net soa dns01.jdc01.pa.comcast.net dnsadmin.comcast.net 1428 900 180 604800 3600
192.168.0.104 Jan 2 21:18:44 Rerror tag 15 ename dns: dns failure 25
192.168.0.104 Jan 2 21:18:44 Tclunk tag 15 fid 318
192.168.0.104 Jan 2 21:18:44 Rclunk tag 15 7
--------
"ip/ping smtp.comcast.net" results in this ip query:
192.168.0.104 Jan 2 21:20:25 Twalk tag 15 fid 166 newfid 295 nwname 1 0:dns
192.168.0.104 Jan 2 21:20:25 Rwalk tag 15 nwqid 1 0:(0000000000000001 74 ) 22
192.168.0.104 Jan 2 21:20:25 Topen tag 15 fid 295 mode 2
192.168.0.104 Jan 2 21:20:25 Ropen tag 15 qid (0000000000000001 74 ) iounit 0 24
192.168.0.104 Jan 2 21:20:25 Twrite tag 15 fid 295 offset 0 count 20 '!smtp.comcast.net ip'
192.168.0.104 Jan 2 21:20:25 dnresolve1 smtp.comcast.net 1 1
192.168.0.104 Jan 2 21:20:25 655.1: sending to 192.168.0.1/local#dns#server0 smtp.comcast.net ip
192.168.0.104 Jan 2 21:20:25 655: rcvd 192.168.0.1 flags: rd ra
192.168.0.104 Jan 2 21:20:25 655: rcvd 192.168.0.1 qd smtp.comcast.net
192.168.0.104 Jan 2 21:20:25 655: rcvd 192.168.0.1 an smtp.comcast.net ip 63.240.76.27
192.168.0.104 Jan 2 21:20:25 655: rcvd 192.168.0.1 an smtp.comcast.net ip 63.240.77.77
192.168.0.104 Jan 2 21:20:25 655: rcvd 192.168.0.1 an smtp.comcast.net ip 204.127.198.27
192.168.0.104 Jan 2 21:20:25 655: rcvd 192.168.0.1 an smtp.comcast.net ip 204.127.202.27
192.168.0.104 Jan 2 21:20:25 655: rcvd 192.168.0.1 an smtp.comcast.net ip 216.148.227.125
192.168.0.104 Jan 2 21:20:25 655: rcvd 192.168.0.1 an smtp.comcast.net ip 216.148.227.147
192.168.0.104 Jan 2 21:20:25 Rwrite tag 15 count 20 11
192.168.0.104 Jan 2 21:20:25 Tread tag 15 fid 295 offset 0 count 1022
192.168.0.104 Jan 2 21:20:25 Rread tag 15 count 39 'dom=smtp.comcast.net ip=216.148.227.147' 50
192.168.0.104 Jan 2 21:20:25 Tread tag 15 fid 295 offset 39 count 1022
192.168.0.104 Jan 2 21:20:25 Rread tag 15 count 38 'dom=smtp.comcast.net ip=204.127.202.27' 49
192.168.0.104 Jan 2 21:20:25 Tread tag 15 fid 295 offset 77 count 1022
192.168.0.104 Jan 2 21:20:25 Rread tag 15 count 38 'dom=smtp.comcast.net ip=204.127.198.27' 49
192.168.0.104 Jan 2 21:20:25 Tread tag 15 fid 295 offset 115 count 1022
192.168.0.104 Jan 2 21:20:25 Rread tag 15 count 36 'dom=smtp.comcast.net ip=63.240.77.77' 47
192.168.0.104 Jan 2 21:20:25 Tread tag 15 fid 295 offset 151 count 1022
192.168.0.104 Jan 2 21:20:25 Rread tag 15 count 36 'dom=smtp.comcast.net ip=63.240.76.27' 47
192.168.0.104 Jan 2 21:20:25 Tread tag 15 fid 295 offset 187 count 1022
192.168.0.104 Jan 2 21:20:25 Rread tag 15 count 39 'dom=smtp.comcast.net ip=216.148.227.125' 50
192.168.0.104 Jan 2 21:20:25 Tread tag 15 fid 295 offset 226 count 1022
192.168.0.104 Jan 2 21:20:25 Rread tag 15 count 0 <no data> 11
192.168.0.104 Jan 2 21:20:25 Tclunk tag 15 fid 295
192.168.0.104 Jan 2 21:20:25 Rclunk tag 15 7
next reply other threads:[~2006-01-03 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 1:50 greg scott [this message]
2006-01-03 9:31 ` Robert Raschke
2006-01-03 12:13 ` Steve Simon
2006-01-03 12:18 ` erik quanstrom
2006-01-03 14:39 ` Russ Cox
2006-01-04 2:28 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bde13d79d0a3adcb1545e5484908131f@comcast.net \
--to=x-x@comcast.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).