Can nsd 2.3.3 make load balancing?
Example:
www 600 IN A 10.0.0.1
600 IN A 10.0.0.2
600 IN A 10.0.0.3
Greet
Sebastian Schikora
Can nsd 2.3.3 make load balancing?
Example:
www 600 IN A 10.0.0.1
600 IN A 10.0.0.2
600 IN A 10.0.0.3
Greet
Sebastian Schikora
Sebastian wrote:
Can nsd 2.3.3 make load balancing?
Example:
www 600 IN A 10.0.0.1
600 IN A 10.0.0.2
600 IN A 10.0.0.3
Hi Sebastian,
No, nsd does not load balance for you.
Round robin sequence of RRset members in consecutive answers
is an explicit NON-requirement for NSD. (from the REQUIREMENTS file).
Best regards,
Wouter
[Quoting "Sebastian", on Feb 24, 10:43, in "NSD 2.3.3 Load Balan ..."]
Can nsd 2.3.3 make load balancing?
Example:
www 600 IN A 10.0.0.1
600 IN A 10.0.0.2
600 IN A 10.0.0.3
What you want for this is random or sequentional reordering of the
recordset on consecutive queries so that resolvers use the different
IP-numbers to spread the load. Most (almost all end-user) resolvers
do not do the recursing themselves, but use caching-forwarders.
Stub-resolvers, which use caching-forwarders, will thus never query
an NSD nameserver, as NSD is authoritative-only.
Caching-forwarders may or may not be setup to reorder.
Now, to answer you question more directly:
NSD does not re-order the recordset, but for load balancing
this is of little importance, as it is the behaviour of the
caching-forwarders which does the trick.
-- ted
Just out of curiosity, what is the order of records in an RRset in a response
The order in which it is listed in a zone file, or alpha-numerical sorted, other ?
Thanks,
Roy
Roy Arends wrote:
Just out of curiosity, what is the order of records in an RRset in a
response
The order in which it is listed in a zone file, or alpha-numerical
sorted, other ?
The order in which it is listed in the zone file.
(unless the same record has been added as an authority/../section
already - I see this in the code I do not have an example of it).
Best regards,
Wouter