>>>>> "Mark" == Mark Andrews <[email protected]> writes: Mark> It is quite common for the stealth masters to exist (not Mark> listed in the NS RRset). It is also quite common for Mark> recursive servers to have local copies of zones that are in Mark> use locally but not be listed in the NS RRset. The update
Mark> Now if you want this to work with the CER turned off while you
Mark> are away and update to the zone to work then protocol work is
Mark> needed to get multi-master working.
mcr> I think that you are saying that there is software work, not that
mcr> there is standards work?
...
Mark> Multi-master (if defined) would do this automatically and
Mark> allow for updates to the zone when partition whether that was
Mark> due to a link failure or powering off of the CER due to
Mark> travel.
Mark> This last part requires standards work as it needs to be cross
Mark> vendor.
Okay, so there would be standards work to do multi-master.
I thought so, but I wasn't clear.
Are there any multi-master implementations using proprietary protocols?
I think that multi-master isn't that important for homenet.
I think that having a stealth master for the reverse ZONE should be a MUST.
Homenet and code point of view, the important requirement would actually be:
CER MUST be able to be authoritative name server for
at least one reverse (ip6.arpa) zone, and at least one
forward zone.
CER SHOULD support zone transfers to a secondary server,
which SHOULD be configurable manually, and SHOULD be
configurable by some TBD DHCPv6 option.
CER SHOULD permit NS records for zones to be configured
manually, and via DHCPv6 option, and SHOULD support
situation where no NS record points at CER itself.
Mark the other part is the update-reverse-zone-by-TCP DNS update,
authorized by TCP. You've talked about this. Do you think we need a
dnsext action to permit this, or any kind of document outside of
homenet?
--
Michael Richardson
-on the road-
pgpuX5rd7Xw2B.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
