Jari, (b) happens automatically and the router in my case is *not* the DHCPv4 server I used on the local network, I use a standalone DHCP server which happens to the DNS server that is authoritative DNS internally. The only thing the router is doing for me is omitting router advertisements that support RFC5006. I believe I can configure the same meaning I can remove the IPv6 address of the DNS server or change the IPv6 address. I will verify the later and circle back to the list.
John ========================================= John Jason Brzozowski Comcast Cable e) mailto:[email protected] o) 609-377-6594 m) 484-962-0060 w) http://www.comcast6.net ========================================= On 9/9/11 1:58 PM, "Jari Arkko" <[email protected]> wrote: >I'm with you with similar setup. But I think this is mostly about being >able to configure your border router with (a) the right DNS server >address for DHCPv4 and (b) the right DNS server address for RFC >5006/DHCPv6. Is your problem that you don't get to do (b)? Or do you skip >(a) as well, and then rely on local multicast naming discovery? > >Jari > >On 09.09.2011 20:29, Brzozowski, John wrote: >> 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 >> > _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
