On Fri, Aug 28, 2015 at 1:29 PM, Juliusz Chroboczek <[email protected]> wrote: >> If you don't like the idea using the NODE NAME TLV to announce DNS >> information of the local hosts, how would you do it without a central >> server configured by a network admin? > > * mDNS plus mDNS proxying; or
you mean a bi-directional proxy between mdns on the host-interface and some distributed DNS services in the home network? > * mDNS over ff05::fb; or Would not work without a multicast routing protocol. > * announce a bunch of dynamic DNS servers (inside or outside the Homenet) > over HNCP, use some ad-hoc registration protocol. This relies on hosts > consulting all of the advertised servers when search for an RR. which still doesn't solve the problem how the hostnames configured on a homenet router gets into one (or multiple) of these DNS servers. > Henning, the flooding part of HNCP is just a multicasting protocol with > some rather unusual characteristics -- marvelously efficient when there is > no churn, bad in the presence of churn. Let's use its strengths and avoid > its weaknesses, not the opposite. Just to be sure, do you see that the hostname of a router or a host would change that often? Henning Rogge _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
