This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jana
Recipients bbayles, ekohl, h.venev, jana, pmoody, ronaldoussoren
Date 2021-04-12.18:02:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618250520.26.0.395907416324.issue30528@roundup.psfhosted.org>
In-reply-to
Content
Running into the same problem here. Within the zonefile rfc1035 defines a usecase for ipv4, but I can't find anything similar for IPv6. The feature is also rather obscure. The zone however is used in the zonefile as origin and in bind in the named.conf to refer to which zone is managed where. 

For this you want to provide the reverse network address, minus the irrelevant zeros, so 192.168.0.0/24 => 0.168.192.in-addr.arpa and 2001:db8::/32 => 8.b.d.0.1.0.0.2.ip6.arpa

This would be to me a fitting and convenient interpretation of the function.
History
Date User Action Args
2021-04-12 18:02:00janasetrecipients: + jana, ronaldoussoren, pmoody, h.venev, bbayles, ekohl
2021-04-12 18:02:00janasetmessageid: <1618250520.26.0.395907416324.issue30528@roundup.psfhosted.org>
2021-04-12 18:02:00janalinkissue30528 messages
2021-04-12 18:02:00janacreate