I’ve been trying to organise reverse DNS for IPv6 addressing through one of the commercial DNS providers (DynDNS), and it’s been an interesting experience. For a start, all of the documentation only mentions IPv4, and generally assumes that you will only be creating single records mapping addresses back to names, rather than handling large ranges of addresses.
Our ISP handles reverse DNS by simply delegating the entire /56 (or /64) to the customer’s DNS provider of choice. That seems fairly reasonable from a business sense since it avoids them having to deal with squillions of potential records, but I think that most customers would have a very small number of reverse mappings required, and ISPs should be more accommodating and allow reverse mappings for individual addresses.
It’s also now the case that the pricing models used by Dyn and other providers need to change. Perhaps it’s just a sales pitch, but I’m being pushed towards a “managed” account that would cope with an old-style /24 (ie. 256 addresses). Given that the base IPv6 allocation to any household will be 10^16 times greater than that, the focus needs to move towards simply letting the customer create the right zones and add records as required.
You’re not a “business customer” any more just because you have hundreds of IP addresses in your control – you’re now just as easily an ordinary consumer. That means that there isn’t a corporate budget that the IT companies can try and suck a fortune out of. Instead small companies, families and individuals with increasingly smaller budgets will be dealing with technologies and data on a scale that was previously only available to the rich. IT companies need to remember that and change with the times.?
Google+: View post on Google+