Ray-san, Thanks for your comments.
> From: Ray Bellis <[email protected]> > Thanks for your note. The idea of running a local authoritative zone > alongside a forwarding proxy or full recursive server has been seen already, > for example in the "dnsmasq" software used by many CPE vendors. I see. DHCP has enough function. RFC 2132 defines DHCP client host name option, and RFC 4702 Section 3.2. "Client Desires to Update A RRs" defines the option to DNS RR. # I'm not aware that DHCPv6 has the same option. Using DHC client host name option is easier than implementing DNS Update client in each client. "dnsmasq" seems to have enough function (except multiple subnets, multiple upstreams). Or a combintion of isc-dhcpd and BIND 9 may achieve all of DNS related works. > It is also listed as requirement LAN.DNS.6 in the Broadband Forum's TR-124 > Issue 2. As such a draft describing this is probably unnecessary. > > Your DNS expertise would of course be much appreciated as we start to tackle > the wider issues around naming in the Homenet, specifically: > > 1. naming updates and queries between subnets One upstream, and multiple subnets case, it may be solved by using one DHCP server and multiple DHCP relay agents. Multiple upstream case, manual configuration is necessary. An end user setup one DNS server which serves local zone and multiple reverse zones. DHCP servers send updates to the DNS server. > 2. integration (or otherwise) of unicast DNS and mDNS It is same as now. Using different TLDs solves the problem. > 3. DNSSEC validation DNS proxy can forward global queries to DNSSEC validators. Local zones does not require DNSSEC validation, I think. I thought to write I-D, but now, DHCP has enough capability, I will consider the issure more. Regards, -- Kazunori Fujiwara, JPRS _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
