JINMEI Tatuya / 神明達哉 wrote
(but my comment is for the OP, AlanS):
If the reason is due to client-side server
selection algorithm (many Unix based resolvers only uses the first
address in /etc/resolv.conf as long as it responds to their queries),
there's basically nothing you can do as the server side operator.
If you also operate the DHCP server(s) from which
the clients obtain the data to put in /etc/resolv.conf,
you can try to balance the resolver load by tuning the
DHCP advertisements.
No-one on the list can really advise whether this would be
useful, as you don't say what problem you're trying to solve,
Best regards,
Niall O'Reilly
University College Dublin IT Services
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
