From owner-freebsd-questions Wed Nov 8 8:49:31 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.bnetmd.net (ns1.bnetmd.net [64.23.0.71]) by hub.freebsd.org (Postfix) with ESMTP id 38A8737B479 for ; Wed, 8 Nov 2000 08:49:29 -0800 (PST) Received: from localhost (freebsd@localhost) by mail.bnetmd.net (8.9.3/8.9.3) with ESMTP id LAA67367 for ; Wed, 8 Nov 2000 11:48:23 -0500 (EST) (envelope-from freebsd@mail.bnetmd.net) Date: Wed, 8 Nov 2000 11:48:23 -0500 (EST) From: Glenn McCalley To: freebsd-questions@freebsd.org Subject: MX-DNS-telnet sanity check Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, more generic than FreeBSD, but hope somecan confirm/deny: We have a domain hosted on us, with an MX record pointing to another ISP. Mail worked just fine until this Monday morning. At that time, mail delivery through the MX'ed ISP went intermittent. By that, some mail is delivered OK, some mail is not. "Other ISP" are claiming that our DNS is set up incorrectly. domain.com. IN MX 0 mail.otherisp.net. --seems pretty straightforward to us, and has worked for over a year. The basis of their claim is their statement that running: bash# telnet domain.com 25 -- does not connect to their mail server, the target of the MX entry, but rather to the server where domain.com is housed. This is supposed to be proof that our DNS MX entry is wrong. Personally, I didn't know that specifying port 25 on a telnet connection would cause telnet to do an MX lookup and then connect to that address rather than the address for "domain.com". Am I missing this or are they blowing the smoke I think they are? Thanks! Glenn. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message