Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Use IPv6 address in PTR records #80
Would be far more "user friendly" if IPv6 addresses could be used directly in the "Name" column for IPv6 PTR zones. I'm coming from the BIND-world, where static text-configuration files where used, and having a /32 IPv6 zone it was quite useful to have different sections in the configuration file for each /64 using
This is not possible in PowerDNS (afaik, at least), so some kind of simplification would be preferred (since we can't use $ORIGIN or sort the list "as we please"). PTR-records could be made using the
And even with the "auto PTR" function, you'd still benefit from showing the actual IPv6 address, rather than the cumbersome entries we have today (dotted string from hell).
The logic would happen server-side within PowerDNS-Admin, and the records would still be stored/sent normally (as dotted strings), but would be converted to/from this format before displaying/storing.
Make it an option to disable/enable (so that it can be introduced as a "experimental feature") that is disabled by default. First implementation might have no error-checks, and imply that the user knows what he is doing. Then at some point; do checks if the IPv6 address actually matches the zone we're editing.
The code does no form of error-checking regarding if the IPv6-address actually is a part of the ip6.arpa domain that's being edited. That's left as an exercise for the user (-:
Also, it only works with
I left out IPv4 on purpose. I'll probably look into that at some point, but IPv6 PTR's was by far first-priority.