From 780872e07eaa735c215765da570d2f1f78bfade7 Mon Sep 17 00:00:00 2001 From: Matthijs Mekking Date: Fri, 13 Mar 2026 11:56:31 +0100 Subject: [PATCH] Don't call dns_zone_setadded() on modify If we are modifiying the zone, the zone must have been added before. Don't overwrite this value on modifications. Also it feels cleaner to pass added=false to configure_zone() in do_modzone(). --- bin/named/server.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/bin/named/server.c b/bin/named/server.c index 8d857eaa60c..dcc2cfe40f1 100644 --- a/bin/named/server.c +++ b/bin/named/server.c @@ -6250,7 +6250,9 @@ configure_zone(const cfg_obj_t *config, const cfg_obj_t *zconfig, /* * Mark whether the zone was originally added at runtime or not */ - dns_zone_setadded(zone, added); + if (!modify) { + dns_zone_setadded(zone, added); + } /* * Determine if we need to set up inline signing. @@ -13057,7 +13059,7 @@ do_modzone(named_server_t *server, dns_view_t *view, dns_name_t *name, dns_view_thaw(view); result = configure_zone(server->effectiveconfig, zoneobj, view->newzone.vconfig, view, &server->viewlist, - &server->kasplist, server->aclctx, true, false, + &server->kasplist, server->aclctx, false, false, false, true); dns_view_freeze(view); -- 2.47.3