---
title: "Host reservations deleted when editing shared networks with Stork"
slug: "stork-hosts-lost-shared-nets"
description: "One of Stork's features is the ability to edit shared networks in Kea DHCP, and shared networks that contain subnets can support host reservations. However, due to a bug in Stork, if you edit a shared network in Stork that contains a subnet, any host reservations associated with that subnet will be deleted if those reservations are defined in the Kea configuration files. Host reservations stored in a database are not affected; neither are host reservations defined outside of shared networks."
updated: 2025-07-24T15:15:58Z
published: 2025-07-24T15:15:58Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.isc.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Host reservations deleted when editing shared networks with Stork

One of Stork's features is the ability to edit shared networks in Kea DHCP, and shared networks that contain subnets can support host reservations. However, due to a bug in Stork, if you edit a shared network in Stork that contains a subnet, any host reservations associated with that subnet will be deleted if those reservations are defined in the Kea configuration files. Host reservations stored in a database are not affected; neither are host reservations defined outside of shared networks.

## AFFECTED VERSIONS

All supported Stork versions — 2.0.x and 2.2.x — are affected. EOL versions back to 1.17.0 are also believed to be affected.

## FIXED VERSIONS

Upcoming 2.3.0 and 2.2.1, which are expected to be released August 6, 2025.

## WORKAROUNDS

Do not edit shared networks using the Stork UI, if the subnets in the network have any reservations defined in the configuration file. Instead, consider one of the following options:

a) Edit the configuration file by hand and restart Kea; or b) Use the Kea API to call to make your changes; or c) Migrate your host reservations to a database.

For the Kea API, one must call `config-get`, modify the result, and then use `config-set` to push the updated configuration. Normally that should be followed by a `config-write` to save the changes. See [https://kea.readthedocs.io/en/kea-3.0.0/arm/ctrl-channel.html#management-api](https://kea.readthedocs.io/en/kea-3.0.0/arm/ctrl-channel.html#management-api) for more information.

Host reservations can be migrated by hand or by using the "Migrate" function in Stork. See [https://kea.readthedocs.io/en/kea-3.0.0/arm/dhcp4-srv.html#dhcpv4-hosts-database-configuration](https://kea.readthedocs.io/en/kea-3.0.0/arm/dhcp4-srv.html#dhcpv4-hosts-database-configuration) and [https://kea.readthedocs.io/en/kea-3.0.0/arm/dhcp6-srv.html#dhcpv6-hosts-database-configuration](https://kea.readthedocs.io/en/kea-3.0.0/arm/dhcp6-srv.html#dhcpv6-hosts-database-configuration) for details about configuring a new hosts database. See [https://stork.readthedocs.io/en/v2.2.0/managing-kea.html#migrate-host-reservations](https://stork.readthedocs.io/en/v2.2.0/managing-kea.html#migrate-host-reservations) for details on migrating host reservations using Stork. Both the "by hand" and Stork methods require the Host Commands hook (see: [https://kea.readthedocs.io/en/kea-3.0.0/arm/hooks.html#libdhcp-host-cmds-so-host-commands](https://kea.readthedocs.io/en/kea-3.0.0/arm/hooks.html#libdhcp-host-cmds-so-host-commands)).

## MORE INFORMATION

[https://gitlab.isc.org/isc-projects/stork/-/issues/1866](https://gitlab.isc.org/isc-projects/stork/-/issues/1866)

ISC support customers are welcome to ask questions via a support ticket.

Thank you for using ISC's software.