Since the DNS server at home only manages its own dns-domain, the dns-server should still use the CPE's IP for external dns query. If user decides not to use the CPE's IP, all dns packets would use the tunnel. If an operator wants to block this, in theory this will require implementing ACL to block dns in AFTR. In practice, this would probably make the user very unhappy.
Draft-ietf-dns-dhcpv4-over-ipv6 addresses a different use case. This will be used when the CPE will be provisioned with a full public IPv4 address (i.e. No NAT in the AFTR). From: Tassos Chatzithomaoglou <[email protected]> Organization: Forthnet Date: Thursday, July 5, 2012 9:06 AM To: Wuyts Carl <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [Softwires] [v6ops] DS-Lite & DNS Since i (as an operator) manage the CPE but not the host, i got a little bit worried and confused by the statement "DNS packets are not expected to go through the AFTR element", since the subscriber can easily send such packets. So my understanding is that this is a supported scenario, but probably not a recommended one. Also, can draft-ietf-dhc-dhcpv4-over-ipv6 be considered an alternative option for passing IPv4 info to clients over IPv6 in DS-Lite networks?
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
