RE: round-robin on bind9.2.1

> From: Steven Job [mailto:list3@wwwcrazy.com]
> Subject: RE: round-robin on bind9.2.1
>=20
> Quoting "Boyack, Kurt" <Kurt.Boyack@pyxis.com>:
>=20
> > Rrset-order was introduced in 8.2 and dropped with 9.1, but=20
> it is not =3D
> > needed to do round-robin; it is used to turn round-robin off.
> >
>=20
> Here is the exact quote from the Bind 9.3 documentation.
>=20
>=20
> 6.2.16.14. RRset Ordering
> When multiple records are returned in an answer it may be=20
> useful to configure
> the order of the records placed into the response. The=20
> rrset-order statement
> permits configuration of the ordering of the records in a=20
> multiple record
> response. See also the sortlist statement, Section 6.2.16.13.
>=20
> An order_spec is defined as follows:
>=20
> [ class class_name ][ type type_name ][ name "domain_name"]
> order ordering
>=20
> If no class is specified, the default is ANY. If no type is=20
> specified, the
> default is ANY. If no name is specified, the default is "*".
>=20
> The legal values for ordering are:
>=20
>=20
> fixed
> Records are returned in the order they are defined in the zone file.
>=20
> random
> Records are returned in some random order.
>=20
> cyclic
> Records are returned in a round-robin order.
>=20
>=20
>=20
> For example:
>=20
> rrset-order {
> class IN type A name "host.example.com" order random;
> order cyclic;
> };
>=20
> will cause any responses for type A records in class IN that have
> "host.example.com" as a suffix, to always be returned in=20
> random order. All
> other records are returned in cyclic order.
>=20
> If multiple rrset-order statements appear, they are not=20
> combined - the last one
> applies.
>=20
> Note: The rrset-order statement is not yet fully implemented=20
> in BIND 9. BIND 9
> currently does not support "fixed" ordering.
>=20

So rrset-order was re-implemnted in a later version of 9.x, but isn't =
round-robin still the default? The original question was how to do =
round-robin, not how to turn it off.