Michael Thomas wrote: > On 02/26/2013 09:10 AM, Ray Hunter wrote: >> >> , but what if there are two edge routers? >> >> Elect one to be authoritative: which needs a new protocol, plus some >> really complex take-over mechanism on failure. > > Pardon my ignorance, but how does this happen in real life, and in > particular with anycast? Aren't all of the anycast reachable servers > authoritative as far as the outside world is concerned? > > Mike > As far as I can see, there are no existing off-the-shelf solutions available that cover all homenet naming requirements.
Therefore to answer your question: it doesn't happen in real life today. We're talking theoretical auto-config of DNS servers by some process. Which would be new and require some sort of election protocol to see which CER would become "the anointed one." That server would then have to work out which zone(s) to serve, given multiple parent ISPs. Also if it failed we'd have to start all over again. Hence the alternative suggestion that all CERs could always become authoritative DNS servers, each providing a zone delegated from their respective parent ISP (or other DNS name service provider). We'd probably then either have to suggest the end nodes update all the servers present in the homenet actively with name->AAAA information via registration every time they moved. Or perhaps more practically, get the host to update a random CER somehow, and then work out some way of mirroring the latest info between zones in the background between the CERs, without needing a static master-slave relationship. That'd probably also require some new stuff. But I'd still rather look at the gap analysis to make DNS work (with new autoconfig/mirroring stuff), than try to proxy mDNS over multiple subnets in an arbitrary topology (messy), or extend mDNS to be multi-subnet aware (completely new, and reliant on site-wide multicast), or extend a stateless protocol like mDNS to update DNS for off-homenet resolution. _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
