|
|
Jim wrote:
On Jul 5, 4:45 pm, Ralph Young <yo...@xxxxxxxxxxx> wrote:
Are there A records set up in your zone file data for the cluster
service hosts in question ? i.e., for the example below, there need to
be A records set up for MALVM3 and MALVM9... in some versions prior
to 5.2, these A records were 'forged'.. with the more complex attributes
(views, multiple formats, etc.) in Bind 9, this is not yet a feature.
The A records need to be manually added...
Is this working on other architectures for you but not I64?
Thanks
-Ralph Young
Process Software
I have not experimented with MultiNet 5.2 on Alpha yet - when I get a
chance I wll.
It has been my experience that prior to MultiNet 5.2 (on VAX and
Alpha), Multinet always forged the A RRs for the cluster serviced name
- so, no there are not A RRs in our zone master file. I take it that
you are suggesting that the zone master file be hosted on the cluster
members who will offer the cluster service as they've been delegated
authority for this name. In the past I've been running these systems
as caching-only DNSes and there has not been any zone master present.
Yes, the A RR records are no long forged just by having the
cluster service logical defined. The nameserver has to be configured
to be a master for the cluster service name and A RR records added for
each member.
Is it expected that an ECO or some future version of MultiNet will
restore that forgery of the A records feature?
I hope so.
regards
Mike
--
+-------------------------------------------------------------------------+
Michael Corbett Email: Corbett@xxxxxxxxxxx
Process Software Phone: 800 722-7770 x369
959 Concord St. 508 879-6994 x369
Framingham MA 01701-4682 FAX: 508 879-0042
|
|