> Is it then out of spec if we're working with a hidden/unreachable master > server, and even though it is disclosed in SOA.MNAME, it is not listed in > NS.NSDNAME ? What should one put in the SOA.MNAME in that case ? Any one > of the slaves ?
Since an RFC 2136 initiator is only supposed to send updates to an NS.NSDNAME, and since the only spec'd use for SOA.MNAME is to select an NS.NSDNAME, any change we want existing clients to make, we'd make with changes in NS.NSDNAME, which would also affect normal operations (since these are used for delegation) which isn't desireable. I don't know a way to get out-of-spec clients to stop sending unwanted updates other than to point SOA.MNAME at a meaningless value like LOCALHOST in one's own local domain, and have that resolve to 127.0.0.1. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
