Hello,

On Tue, May 15, 2001, 10:47:14 GMT
  Joe Wagner, <[EMAIL PROTECTED]> wrote:

>Dmitry Akindinov stroll across the digital landscape and wrote:
>> >> domain1.com.  MX 10 mail.domain1.com.
>> >> domain1.com.  MX 20 mail2.domain1.com.
>> >> domain1.com.  MX 20 mail3.domain1.com.
>> >>
>> >> My router entry on the secondaries re:
>> >> domain1.com = domain1.com.smtp
>>
>>With the .smtp suffix the right part should be A or CNAME record name - MX
>>lookups are not done for names endinf with .smtp
>Oh, I didn't know that, thanks Dmitry.  I see...just to make sure then:
>
>The router on the secondaries shown above should still be:
>          domain1.com = mail.domain1.com.smtp

This is OK, but not necessary - the server may get the same info from DNS MX records.

>The router on the primary should be (something like):
>         domain1.com = local.mailserver-name.com
>         [and]
>         mail.domain1.com = local.mailserver-name.com
>with the second line necessary to catch the forwarded email from the
>secondaries?

I believe it's not necessary but won't harm.

>If I specify the actual A record name of the primary then I shouldn't get
>the looping. Is it in fact out of spec to have two secondaries with the
>same priority? I note most if not all of the major domains I checked have
>duplicate values for their secondaries, which proves nothing of course but
>still...

It's ok to have several MX records with the same priority.


Best regards,
Dmitry Akindinov

=======================================================================
When answering to letters sent to you by the tech.support staff, make
sure the original message you have received is included into your reply.

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>

Reply via email to