From: Petr Špaček Date: Tue, 21 Oct 2025 07:18:03 +0000 (+0200) Subject: Remove stub chapter about load balancing from ARM X-Git-Tag: v9.21.15~52^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=485e04aa7ee0cbe1d354ab2deb4965b2dbb26b1a;p=thirdparty%2Fbind9.git Remove stub chapter about load balancing from ARM Clearly Support wants this in Knowledge base, so let's comply. Related: !6610 --- diff --git a/doc/arm/config-resolve.inc.rst b/doc/arm/config-resolve.inc.rst index fcfa97e20d7..31fab3482bd 100644 --- a/doc/arm/config-resolve.inc.rst +++ b/doc/arm/config-resolve.inc.rst @@ -531,36 +531,3 @@ hierarchy (does not use the public network) for any recursive query for which: All other recursive queries will result in access to the DNS hierarchy to resolve the query. - -.. _load_balancing: - -Load Balancing --------------- - -A primitive form of load balancing can be achieved in the DNS by using multiple -resource records (RRs) in a :ref:`zone file` (such as multiple A -records) for one name. - -For example, assuming three HTTP servers with network addresses of -10.0.0.1, 10.0.0.2, and 10.0.0.3, a set of records such as the following -means that clients will connect to each machine one-third of the time: - -+-----------+------+----------+----------+----------------------------+ -| Name | TTL | CLASS | TYPE | Resource Record (RR) Data | -+-----------+------+----------+----------+----------------------------+ -| www | 600 | IN | A | 10.0.0.1 | -+-----------+------+----------+----------+----------------------------+ -| | 600 | IN | A | 10.0.0.2 | -+-----------+------+----------+----------+----------------------------+ -| | 600 | IN | A | 10.0.0.3 | -+-----------+------+----------+----------+----------------------------+ - -When a resolver queries for these records, BIND rotates them and -responds to the query with the records in a random order. In the -example above, clients randomly receive records in the order 1, 2, -3; 2, 3, 1; and 3, 1, 2. Most clients use the first record returned -and discard the rest. - -For more detail on ordering responses, refer to the -:ref:`rrset-order` statement in the -:namedconf:ref:`options` block.