> What you understand as "crazy talk," I see as; trying to get something > working, in best-effort mode, taking into account the limitations of a > home network with a CE router in front of it.
Then again, the point of this WG as I understand it is to get rid of some of those limitations, not to accomodate or perpetuate them. :) > We assume that a DynDNS-style approach simply will never scale for every > IPv6 address in the home, and therefore the home router has to be > authoritative, handling the requests. You can have a router be authoritative for its own zones and also have a reliable secondary name service elsewhere. I run BIND 9 on my home router (netgear wndr3700 running customized openwrt/cerowrt, thank you Dave Taht); it's authoritative for several zones, both forward and reverse, some of which are split into internal and external views, and all of which are DNSSEC signed. When any of the zones is updated due to the addition or removal of a device, a NOTIFY is sent to the secondary name service, which IXFRs up the changes. (I use ISC's SNS for this because I'm an employee and get it for free, but there are similar inexpensive services out there including, IIRC, a recent offering from Amazon -- and it wouldn't be a difficult service for an ISP to offer.) For queries originating inside my network, the router handles recursion and will answer authoritatively when asked for a name in the site-local namespace or in the internal view of the public namespaces. Queries originating outside the network generally go to the secondary servers. If I'd wanted to, I could have configured my router to be a hidden master, and then *all* the queries would go to the secondaries (except for *XFR requests coming from the secondaries). So in this model both the router and the secondary servers are authoritative for the externally visible view of the network; the router is solely authoritative for the internally visible view. I don't know of any reason this approach couldn't scale. -- Evan Hunt -- [email protected] Internet Systems Consortium, Inc. _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
