On Fri, Aug 28, 2015 at 9:49 AM, Markus Stenberg <[email protected]> wrote: > On 28.8.2015, at 10.02, Henning Rogge <[email protected]> wrote: >> So what IS the proposed solution for a decentralized HNCP configured >> homenet to share local "configured" DNS names with the rest of the >> homenet? > > For sharing in general, there are two methods (as far as HNCP goes); > > - publish a DNS Delegated Zone TLV that points to a (local or remote) DNS > server that responds for that zone.
central server sounds bad for "distributed network". > - publish Node Name TLVs for individual nodes (won’t scale forever, but > possibly enough). That could work... still, if every DNCP node publishes a DNS name for the node (and maybe another one for a few locally attached non-DNCP hosts) this would increase the size of the DNCP database a little bit. Wasn't there a size limit for the database (or was it per node?)? > If the node that has configured state _is not_ running HNCP, then options > boil down to: > > - DHCPv6, mDNS assuming first-hop router cares and does DHCPv6/mDNS (shncpd, > cough) > - DNS-update aimed at the right place (+ injection of DNS Delegated Zone TLV > per zone somewhere in the HNCP cloud) Yes, this would be more complex. But pushing the local router as a nameservice would be enough to inject the knowledge of the HNCP cloud to the attached hosts. Henning Rogge _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
