Malcolm Dunnett wrote:
$ttl 300
@ 604800 IN SOA vmscluster.viu.ca.
Postmaster.mala.bc.ca. (
2 ; Serial
7200 ; refresh every 2 hours
3600 ; retry every hour
12096000 ; expire in twenty weeks
300 ) ; minimum TTL
604800 IN NS malvm3.viu.ca.
IN NS malvm9.viu.ca.
MALVM3 IN A 142.25.103.73
MALVM9 IN A 142.25.103.71
but this didn't work - I get a
"*** No address (A) records available for VMSCLUSTER.VIU.CA"
What am I doing wrong?
never mind - I figure it out, I need to put :
@ IN A 142.25.103.73
@ IN A 142.25.103.71
ie give the A records to the cluster alias, not the actual hosts.
This wouldn't really be the best solution as one of
the nice things about the cluster service names was that you could
automatically add and remove nodes from the service (eg if a node
went down the address of that node would go away ) and conversely
adding a node would add that address. How would this work with
manual A records? Would the non-existant hosts still show up at
the end of the list?
Figured this out too: the answer is no, the hosts that aren't up
(actually those that don't have their DNS running) will not
show up in the cluster alias even if they're defined in the
zone file. So having to set up the zone information and add
all the potential IP addresses isn't really that big an issue.
One thing that I still haven't figured out is if there's a way
to change the ttl on the cluster alias records. It appears the
ttl is always 5 minutes, regardless of the entries in the
zone file. This seems rather odd as I found a document on the
net (at http://www.process.com/techsupport/multinet/787/46.html )
that indicates the timers are much shorter for the actual
load average updates. With a 5 minute ttl it could take up to
5 minutes for the DNS to recognize that a node has come or
gone, whereas it appears the actual cluster alias service
will notice in about 1 minute - so why not make the ttl 1 minute
also?
|