Bugfix/Feature Release 1.3.1
What's Changed
- Fix embedded tables by @peteeckel in #623
- Fix incorrect mask warning by @peteeckel in #627
- Allow multiple address records per PTR record by @peteeckel in #630
Full Changelog: 1.3.0...1.3.1
Breaking Change
There is a breaking change in the data model that was required to properly fix #624.
The root cause for that issue was that there was an OneToOneField
mapping address records to their PTR records. In fact, this is not a 1:1 relationship, but under certain circumstances more than one address record can relate to the same PTR records, for example address records for name servers in a child zone and the corresponding glue records in the parent zone.
For this reason, ptr_record
was modified to use a ForeignKey
instead, and as a consequence now the address_record
reverse relation is named address_records
instead and can map to multiple address fields. This might require minor changes to API clients and scripts.