LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (1100 bytes) , application/pgp-signature (217 bytes)
Print Reply
Mime-Version:
1.0
Sender:
LISTSERV give-and-take forum <[log in to unmask]>
Date:
Thu, 22 Jun 2000 10:47:22 -0400
Reply-To:
LISTSERV give-and-take forum <[log in to unmask]>
Subject:
From:
Valdis Kletnieks <[log in to unmask]>
Content-Transfer-Encoding:
7bit
In-Reply-To:
Your message of "Wed, 21 Jun 2000 17:05:55 PDT." <[log in to unmask]>
Content-Type:
multipart/signed; boundary="==_Exmh_1464362666P"; micalg=pgp-sha1; protocol="application/pgp-signature"
Comments:
On Wed, 21 Jun 2000 17:05:55 PDT, Joseph McDonald <[log in to unmask]>  said:

> If Listserv doesn't like the above setup, your best route would probably be
> to make your A record with the name "listserv.uic.edu" (and if you still
> want "machine1.uic.edu" to be in existence, make that one your CNAME).  Be
> sure to remove the MX record if you make "listserv.uic.edu" an A record.

Um. No. You *leave* the MX in there, as follows:

listserv.uic.edu.  MX 0 listserv.uic.edu.

This way, a remote host mailing to you will *GET* the MX record
on the first DNS lookup (it is *REQUIRED* to do an MX lookup first).
Any reasonable DNS server will also tack the A record for the machine
into the 'additional info' field of the DNS reply.  Thus, you get
the A record you actually want to send to on the FIRST query.

If you don't have an MX, then the remote site has to ask for the MX,
get a negative answer, and THEN ask for an A record.

Twice the DNS traffic.  You don't want that.

--
                                Valdis Kletnieks
                                Operating Systems Analyst
                                Virginia Tech



ATOM RSS1 RSS2