[309] in Hesiod

home help back first fref pref prev next nref lref last post

Re: Info please

daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Fri Jul 19 14:59:33 1996

Date: Fri, 19 Jul 1996 14:58:53 -0400
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: asafier@csc.com
Cc: hesiod@MIT.EDU
In-Reply-To: Adam Safier's message of Fri, 19 Jul 1996 13:24:49 -0700,
	<31EFEF11.2C28@csc.com>

   Date: Fri, 19 Jul 1996 13:24:49 -0700
   From: Adam Safier <asafier@csc.com>

   Please send me info on how to get more info on using hesiod records in 
   DNS.

   Specifically, I'm interested in using DNS to control the sequence of 
   connect attempts to a primary and backup server.  I'm NOT looking for 
   round-robin load balancing.  I want all connection attempts to go to the 
   primary and only go to the secondary if primary is down.

What you're looking for is a DNS issue, not a Hesiod issue --- and I
don't know of any way to make DNS do what you're looking for.  In
general, DNS is architected to do round-robin load balancing, since in
general's it's the right thing to do.  I don't know off-hand of any way
of forcing it to do something that's sub-optimal.

							- Ted

home help back first fref pref prev next nref lref last post