MX priority
keith at mail.telestream.com
keith at mail.telestream.com
Tue Aug 1 15:57:29 UTC 2000
That wasn't the question I asked. I asked what the values meant. I
understand the priority preferences just not the actual value meaning.
I found the answer though in the O'reilly bind book pages 92 - 99.
For the archive:
The part I've always known....
It's the priority the servers are assigned that make the difference. 0
being lower then 10. 10 being lower then 20 set's preference to the lower
value and failover to the higher.
The part I needed to learn....
The values are MEANINGLESS. If your primary is set to 0 and your
secondary is set to 10. It has no functional difference than if your
primary is set to 0 and secondary to 50.
I had thoughts that a greater span of the primary and secondary values
would cause something different to happen. Like maybe a longer delay
before failing over to a lower priority. Nope.. The book actualy states
on page 93.
"The preference value itself isn't important, only it's relationship to
the values of the other mail exchangers".
Keith
=================================
Keith W.
At the helm <for better or worse>
My non work related site
www.cydonia.net
=================================
On Tue, 1 Aug 2000, Nicolai Langfeldt wrote:
>
> keith at mail.telestream.com tastet:
> > In MX priorities, what exactly are the priority values doing? For
> > instance If the primary is set to a 0 value and the secondary is set to a
> > 10 value. What would the differnce be if the secondary were set to a 20
> > or something? Any difference at all ?
>
> They are used for sorting the MXes only. So the pri value for your
> primary MX should be lower than for the secondary.
>
> Nicolai
>
>
>
>
>
More information about the bind-users
mailing list