DNS cluster address additions for internal communication

Question

Hi Guys,
          My understanding is that WL cache's DNS address of the cluster, and removes
          'dead' cluster members.
          I imagine that this means that if I use:
          ic = new InitialContext("t3://myclusteraddress:7003");
          and I have myclusteraddress mapped to 10.0.0.1 and 10.0.0.2 that all will be
          well with the world?
          And if 10.0.0.1 goes down, all will still be well?
          What happens when I dynamically add a server to such a cluster? As the
          DNS doesn't get read again, cos
          it's cached, what happens? Is there some magic that goes on behind my back
          perhaps involving multicast of
          new servers that updates the "DNS cache" so that the new server is included?
          For external clients, I understand the problem, and the need for a hardware
          load balancer or the like that
          can detect failure and not return dead DNS servers. Qustion: Can I emulate
          this using a piece of software?
          Regards,
          Q
          

Answer 1

As requested:
// Include keys file
include "/etc/rndc.key";
// Declares control channels to be used by the rndc utility.
// It is recommended that 127.0.0.1 be the only address used.
// This also allows non-privileged users on the local host to manage
// your name server.
// Default controls
controls {
inet 127.0.0.1 port 54 allow {any;} keys {
"rndc-key";
options {
directory "/var/named";
recursion false;
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
// query-source address * port 53;
// # Adding this...
forwarders {
151.164.8.201;
151.164.1.8;
forward first;
// # to here..
// a caching only nameserver config
zone "." IN {
type hint;
file "named.ca";
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
zone "" IN {
file ".bak";
masters {
type slave;
zone "kccompany.org" in {
file "kccompany.org.zone";
type master;
zone "200.168.192.in-addr.arpa" IN {
file "db.192.168.200";
type master;
zone "xxx.207.64.in-addr.arpa" IN {
file "db.64.207.xxx";
type master;
logging {
category default {
defaultlog;
channel defaultlog {
file "/Library/Logs/named.log";
severity info;
print-time yes;
};