On 31.8.2015, at 13.37, Henning Rogge <[email protected]> wrote: > On Mon, Aug 31, 2015 at 12:34 PM, Markus Stenberg > <[email protected]> wrote: >> On 31.8.2015, at 13.16, Henning Rogge <[email protected]> wrote: >>> Typical configuration of a cheap router would be to run dnsmasq for >>> local DHCP and as a DNS cache. If each of these DNS caches could >>> forward DNS queries for *.<homenet-router-id>.homenet to the relevant >>> homenet router, it would not be necessary to pool all the information >>> in an elected DNS “master". >> For naming this works as is fine in our current implementation too; all you >> get is some duplicates (foo.link1.rid1.home and foo.link2.rid2.home may both >> exist, even if link1.rid1 is same link as link2.rid2). > You mean that a Homenet user use a switch to connect two Homenet > routers AND a Host ? > > Or maybe a Host with two interfaces connected to two Homenet routers?
Let’s assume a shared link with 2 homenet routers (rid1, rid2) and 1 host (foo). Given no election, use of e.g. mDNS to determine hosts/services would result in the host showing under both rid1.home and rid2.home. That isn’t a problem in naming case (you have IP => name, and name => IP resolving), but for service discovery it kind of sucks. -Markus _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
