It appears that Paul Vixie <p...@redbarn.org> said:
-=-=-=-=-=-
None of the above. Do what RFC 2136 does to send updates to the primary
authority, or do what RFC 1996
does to send notifications to all listed authorities. Any new signaling is
effectively a way to go out
of band. The system is complete as it is.
Without manual configuration, how is the child supposed to know where to find
the stealth parent to notify?
Neither of the mechanisms Paul suggested require manual configuration.
I am clearly missing something here. The child zone wants to notify the
parent to tell it to pick up some new DNSSEC keys or something. The
parent's NS are A, B, and C, but the notify needs to go to stealth server
X or maybe registrar server R.
How does the child know where to send the notification?
R's,
John:
PS: I see that 1996 says:
Stealth .... A
stealth server will only be known by other servers if
they are given static configuration data indicating
its existence.
Notify Set set of servers to be notified of changes to some
zone. Default is all servers named in the NS RRset,
except for any server also named in the SOA MNAME.
Some implementations will permit the name server
administrator to override this set or add elements to
it (such as, for example, stealth servers).
That sure looks like manual configuration to me.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
