In message <504f65c7.4010...@mtcc.com> Michael Thomas writes: > On 09/11/2012 09:01 AM, Ted Lemon wrote: > > > There are a couple of options being pursued in the DHC working > > group; the DHCP address registration process would be an obvious > > mechanism for leveraging DHCP to populate the DNS. The idea here is > > that you do RA+SLAAC, or RA+CGA, and then you contact the DHCP > > server to tell it what address you allocated and what name you want > > associated with it, and to get any local network configuration > > information you might need. > > Maybe somebody can educated me, but isn't it a bit dangerous to use an > auto-configured address as a way to contact a host? If I change out my > ethernet hardware, for example, my auto-conf address would normally > change too, right? > > > However, of course this is new technology that isn't even > > standardized yet. I'd like it if homenet recommended implementing > > this, but I think another way of populating the DNS is through mDNSw > > hen a host publishes its name in mDNS, it's assumed to be valid as > > long as no conflicting registration has been made locally. I don't > > particularly love this method because mDNS doesn't have the same > > duplicate detection features that DHCP does through the DUID, but it > > wouldn't be _worse_ than plain mDNS, and would allow the DNS > > resolver to query a consistent FQDN tree for local names, so that it > > would work whether you were attached to the local wire or not. > > DHCP may be a solution but it ought not be the only solution, right? > What if there's no relationship between my dns repository and the DHCP > server? That is, suppose that Google hosted my DNS and thus wasn't > actually on my home network. I suppose that a home router could work > in concert by either working with its DHCP or listening to mdns > chatter and then doing IXFR's to a name server. Is that what's being > talked about? > > Mike
Mike, > suppose that Google hosted my DNS Create a zone names <myhome>.<mydomain-at-google-ns> and then you can have a zone for which dyn-DNS is authoritative. At that point the dynDNS server and DHCP server need not be the same host, just both under your control and able to use the dynDNS protocol to populate the dynDNS domain (the <myhome> subdomain in the prior example). Unless of course you can convince Google to honor dynDNS from your DHCP server (hint: no chance, create a subdomain if you want dynDNS). If Google is a secondary, not primary, then problem solved. Personally I have stayed away from mDNS, compiling out avahi (mDNS) or bonjour or anything similar in any port that offerred it. Curtis
_______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
