Your problem is that your .local [1] auth server is only available over IPv4? Or said another way, your problem is that your IPv6 auth server is different from your IPv4 auth server, and only the IPv4 version is authoritative for .local?
I'd say this is a too-specific example of a valid problem case. We should say that the home gateway should be (by default) authoritative for .local [1] in both IPv4 and IPv6. If you want to configure separate resolvers with different views, or define different auth servers for .local in IPv4 and IPv6, then your breakage is your configuration problem, not a spec problem. Lee [1] Or whatever, home users with global domain names are a corner case. Substitute appropriate local zone if .local becomes unusable. > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Brzozowski, John > Sent: Friday, September 09, 2011 1:30 PM > To: [email protected] > Subject: [homenet] DNS and IPV6 within the home > > Wanted to share something here to get some feedback and to determine if > this is something that is in scope for HOMENET. > > Consider the following: > > * dual stack home network > * private IPv4 > * global IPv6 > * local DNS that resolves local hosts, this data is not available > authoritatively on the Internet > > My home router supports RFC5006 (not sure the RFC was revised when the > router firmware was developed). There is an IPv6 DNS server configured on > the router which is transmitted in the router advertisements. > > A host on the network supports RFC5006. > > When the host attempts lookups for local resources using the global IPv6 > DNS server address it recurses to the Internet and never gets the answer > it expects for the local network resources. The client resolver also > never attempts to contact the local, private IPv4 DNS server since the > IPv6 DNS is technically responding. Explicit DNS queries to the local, > private DNS servers work but this not really usable. > > Ultimately I had to disable DNS over IPv6 to ensure local and Internet > resources are resolvable. > > In this case the local IPv4 DNS server is a separate server, frankly I am > not sure if having them be the same device ie the home router would make a > difference. I suppose this would depend on the router's DNS capabilities. > > It seems to me that this situation is bound to crop more up as IPv6 > deployments increase. > > John > ========================================= > John Jason Brzozowski > Comcast Cable > e) mailto:[email protected] > o) 609-377-6594 > m) 484-962-0060 > w) http://www.comcast6.net > ========================================= > > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
