Ah, thanks. So, this could be used, but would give limited functionality to links served only by router b.
The right solution will involve using hncp, I hope, to elect the primary server for the network, and all updates would be sent to that server. Other router could act as secondaries, or just forward DNS messages to the nearest (or any) primary or secondary. I think the election process is probably the hardest thing in this solution, and I am hoping someone already knows how to do it... :) On Jul 18, 2016 20:33, "Markus Stenberg" <[email protected]> wrote: > > On 18.7.2016, at 19.55, Ted Lemon <[email protected]> wrote: > > Right now HNCP doesn't actually seem to have a TLV for advertising > resolvers. How does this work now? > > DHCP options have also DNS server options (for v4 and v6). > > -Markus
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
