From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, greg scott <x-x@comcast.net>
Subject: [9fans] smtp dns failure: mx lookup
Date: Tue, 3 Jan 2006 06:18:38 -0600 [thread overview]
Message-ID: <20060103121838.1ED253256D@dexter-peak.quanstro.net> (raw)
In-Reply-To: <bde13d79d0a3adcb1545e5484908131f@comcast.net>
dns is working just fine. there is no mx record for
smtp.comcast.net. (dig smtp.comcast.net mx on linux). it shouldn't
work after the ping, either.
comcast should have this record in their database:
smtp.comcast.net. $TTL in mx smtp.comcast.net.
i suffered the same problem when setting up my domain.
the solution is probablly to add smtp.comcast.net in your ndb
database. maybe upas should lookup the a/aaaa record if there's
no mx record as a fallback. i'd be careful about doing that, though.
- erik
next prev parent reply other threads:[~2006-01-03 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 1:50 greg scott
2006-01-03 9:31 ` Robert Raschke
2006-01-03 12:13 ` Steve Simon
2006-01-03 12:18 ` erik quanstrom [this message]
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=20060103121838.1ED253256D@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=x-x@comcast.net \
/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).