I see two ways to fix this:
- we can fix this in the packaging and avoid adding the entry in /etc/bind/named.conf.local if it's already there
or
- we can fix the 'get_named_conf' command so that it won't include the snippet if it's already there. Maybe we could use write_custom_config_section (src/provisioningserver/utils.py) but I wonder if we can manage the upgrade properly.
I see two ways to fix this: named.conf. local if it's already there config_ section (src/provisioni ngserver/ utils.py) but I wonder if we can manage the upgrade properly.
- we can fix this in the packaging and avoid adding the entry in /etc/bind/
or
- we can fix the 'get_named_conf' command so that it won't include the snippet if it's already there. Maybe we could use write_custom_