Activity
Newest
Oldest
Adam
How much progress has been made on IPv6 since your last update in November 1, 2018, almost 2 years ago? This is becoming a critical issue.
Sean
Any update here, we are full IPv6 dual-stack w/ IPv4.
Adam
Any updates or ETA? This is a critical feature on the modern web!
IPv6 support was first marked "Planned" almost two years ago, in February 2018, and the last DNSFilter comment on this was over a year ago in November 2018.
Mike
Please advise any updates on DNS support?
Adam
Any updates on IPv6 support in the last 7 months?
Mike Schroll
We will first support IPv6 with our user agents: Android, Windows, and LAN Proxy.
Adam
@Mike Schroll: Timeframe for agent support and then resolver support?
Mike
Initial support for this is expected to support entering a /64 -- Looking for feedback on whether this works or doesn't work for customers
Adam
@Mike: Any timeframe for IPV6 support? Is there beta access?
Mike
@Adam: No time-frame yet -- but we'll reference this feature request and let you know once we have it available for testing!
Mike
@Adam: Probably Q3 or Q4 of this year.
Mike
@Adam: Some byte limits in our current architecture.
Adam
@Mike: Are you on a timescale of weeks, months, or years? I am in a trial and this may be a deciding factor.
Adam
@Mike: Why only a /64?
First Name
@Mike: This is good to hear!
Adam
@Jason Wiegel: Not sure why you replied to me, I'm just another customer.
However, a /112 IPv6 prefix breaks many aspects of IPv6. IPv6 subnets should not be smaller than a /64 in most cases. You should get your ISP to allocate you at least a /64. Even Comcast (barely) Business Coax gives out a /56, and their residential gives out a /64!
For some explanation, see: https://etherealmind.com/allocating-64-wasteful-ipv6-not/
Jason Wiegel
@Adam: We are enterprise and my ISP provided me with /112.
Adam
@Mike: Any updates on timeframe?
Justin
+1 for me! I definitely feel this will become very important in the next 5 years
Ken Carnesi
planned