That's essentially what I'm getting at. If the v6 addresses/blocks are allocated in a similar fashion to IPv4, where the octets are clearly named by state and "hsd1", then I don't see why they should lack PTR. However, even if they're not assigned or delegated in that way, it'd be helpful to have SOME form of PTR on there. Otherwise, they'd be a lot like Google, leaving the traceroute and end-point PTR left up to our imagination (even though it's available internally to Google employees). I understand why Google lacks PTR to some extent with anycast and the mobility of their v4 addresses, but I suspect that Comcast isn't doing anything that sophisticated. On Wed, Oct 9, 2013 at 11:47 AM, Robert Webb <rwebb@ropeguru.com> wrote:
On Wed, 9 Oct 2013 11:41:50 -0500 Chris Adams <cma@cmadams.net> wrote:
Once upon a time, Blair Trosper <blair.trosper@gmail.com> said:
Does anyone know why (or can someone from Comcast explain why) there is no PTR on their residential/business IPv6 addresses?
I believe business customers (with a static assignment) can request reverse DNS entries. Residential customers are not guaranteed a static assignment, so they can't get reverse set.
-- Chris Adams <cma@cmadams.net>
But how would thet differ from the IPv4 address space which has PTR records for all their IP's? Just the shear number they would have to deal with in the IPv6 space?
Robert