everyone-- Before we get too far down the road dreaming up how to register names for hosts on home networks, I'd like to suggest gently that a related problem, i.e. how to register authoritative name services for the subdomains of ip6.arpa corresponding to prefixes delegated to home networks, is a lot more pressing.
For your consideration, my personal home server currently resides at 2001:5a8:4:2290::102. Here's what dig -x currently returns for that IPv6 host address: > $ dig -x 2001:5a8:4:2290::102 > > ; <<>> DiG 9.8.1-P1 <<>> -x 2001:5a8:4:2290::102 > ;; global options: +cmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2427 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;2.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.9.2.2.4.0.0.0.8.a.5.0.1.0.0.2.ip6.arpa. IN > PTR > > ;; ANSWER SECTION: > 2.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.9.2.2.4.0.0.0.8.a.5.0.1.0.0.2.ip6.arpa. > 86400 IN PTR grymling.conjury.org. > > ;; Query time: 371 msec > ;; SERVER: 2620:149:5:f09::53#53(2620:149:5:f09::53) > ;; WHEN: Mon Jul 30 11:43:57 2012 > ;; MSG SIZE rcvd: 124 The steps I had to go through to be sure that such queries were answerable were not the steps I would want to defend in a feature usability review. I realize that solving this problem with a standard would involve more working groups than HOMENET, but clearly the effort needs to start here. Once we have a good idea how to solve this problem, then I think it will be easier to talk about forward DNS coherently. -- james woodyatt <[email protected]> member of technical staff, core os networking _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
