Date: Wed, 8 Nov 2000 14:31:16 -0600 From: Goblin <h0b_g0blin@yahoo.com> To: Glenn McCalley <freebsd@mail.bnetmd.net> Cc: freebsd-questions@freebsd.org Subject: Re: MX-DNS-telnet sanity check Message-ID: <20001108143116.A19030@uswest.net> In-Reply-To: <Pine.BSF.4.21.0011081130350.66705-100000@mail.bnetmd.net>; from freebsd@mail.bnetmd.net on Wed, Nov 08, 2000 at 11:48:23AM -0500 References: <Pine.BSF.4.21.0011081130350.66705-100000@mail.bnetmd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable They are, tol put it kindly, misinformed, and ignorant. Is your mail being bounced? To which domain is mail being lost? What is your mail server running? I have a little experience in this, moreso in the problems associated with firewalled MTA hosts. (This is bad in itself, BTW) As for MX records, your domain does not need a CNAME to a mail server, as the whole idea of MX records is being able to specify one mail server which is an actual host for either multiple other hosts not intended to be MTAs, or for a domain to simplify email addresses. As for your DNS configuration, upon request, I can dig into yours and see what I find. On 11/08, Glenn McCalley rearranged the electrons to read: > Hi all, more generic than FreeBSD, but hope somecan confirm/deny: >=20 > 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. >=20 > "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. >=20 > The basis of their claim is their statement that running: >=20 > bash# telnet domain.com 25 >=20 > -- 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. >=20 > 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. >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message Your eyes are weary from staring at the CRT. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise. --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6CbgTubgCGkrWpN4RAgL5AKClf25wnbaDtiQ0L9YKk2Wod3jrPgCgoh9y ffLGW8d3yrDEpok/j42AM5Q= =GZjI -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001108143116.A19030>