Time Warner Cable Native IPV6 DNS issue with Merlin 376.49 on RT-AC56U

[PabloAbonia]

TWC for some reason does not provide an IPV6 DNS address, and rather routes all DNS queries to an IPV4 address, that provides both IPV4 and IPV6 answers.

I suspect that some scripts are not being completed in this situation: no IPV6 DNS address from ISP, therefore certain scripts are not run, even if I fill out those addresses with 3rd party DNS from OpenDNS or GoogleDNS.

This leads to a mostly broken IPV6 implementation which works randomly and occasionally. In particular MTU size seems problematic, which leads me to suspect that there the firewall is blocking ICMP MTU address messages.

Ordinarily this would not be such a problem if not for the MTU issue, and TWCs habit of changing the prefix between reboots of the router.

I'lol keep looking into this, but firewall setup for ICMP is a little beyond me.

Has anyone had a similar experience with TWC or IPV4 only DNS?








--
Pablo

 

[BigIronPops]

As I understand it, TWC's IPv6 implementation is not really in "production mode" yet, so some users experience quite a bit of churn with IPv6. Yes, they have rolled it out to a lot of customers, but it's apparently not considered "production".

TWC for some reason does not provide an IPV6 DNS address, and rather routes all DNS queries to an IPV4 address, that provides both IPV4 and IPV6 answers.

I suspect that some scripts are not being completed in this situation: no IPV6 DNS address from ISP, therefore certain scripts are not run, even if I fill out those addresses with 3rd party DNS from OpenDNS or GoogleDNS.

This leads to a mostly broken IPV6 implementation which works randomly and occasionally. In particular MTU size seems problematic, which leads me to suspect that there the firewall is blocking ICMP MTU address messages.

Ordinarily this would not be such a problem if not for the MTU issue, and TWCs habit of changing the prefix between reboots of the router.

I'lol keep looking into this, but firewall setup for ICMP is a little beyond me.

Has anyone had a similar experience with TWC or IPV4 only DNS?








--
Pablo

 

[DallasFlier]

Here in the Dallas, TX area, my RT-AC68U can't even obtain an IPv6 address from TWC - I turned it on in the router a while back, but have never been able to successfully obtain an address.

 

[cockytrumpet]

Must be a regional thing. I've had the same /64 from TWC since I first enabled it on the router and after many reboots. I can't speak for TWC's DNS. I've been using dnscrypt on the router for v6 from day 1.

 

[jegesq]

I don't think it is TWC that is the issue. I am in Southern California and my ipv6 from TWC works just fine on Merlin 374.38 and .41. I upgraded to 376.49 and ipv6 was broken. Could not obtain any address using "Native" setting. Downgraded back to 374. and ipv6 is working again. Something is amiss in 376.49.