Merge ~bjornt/maas:bug-1908087-disable-empty-zones into maas:master
Proposed by
Björn Tillenius
Status: | Merged |
---|---|
Approved by: | Björn Tillenius |
Approved revision: | b0330dd3488d06ae835b31155692b4b46e5c0d6a |
Merge reported by: | MAAS Lander |
Merged at revision: | not available |
Proposed branch: | ~bjornt/maas:bug-1908087-disable-empty-zones |
Merge into: | maas:master |
Diff against target: |
34 lines (+2/-3) 2 files modified
src/provisioningserver/dns/tests/test_actions.py (+1/-2) src/provisioningserver/templates/dns/named.conf.options.inside.maas.template (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alberto Donato (community) | Approve | ||
MAAS Lander | unittests | Pending | |
Review via email: mp+398953@code.launchpad.net |
Commit message
LP #1908087 - Reverse DNS for non-maas RFC1918 zones fails inside maas
Considering MAAS is usually configured to point to another DNS within a
DC, having empty-zones-enable set to 'no' makes the most sense.
Especially since that was the behaviour in bind9 before MAAS 2.9.
In the future we might want to make this optional.
To post a comment you must log in.
+1