I'm baffled by something strange I came across yesterday, and would appreciate an injection of clue.
I've kept this message short. Of course I can give more detail, but it's not yet clear what might be useful enough either to merit imposing a longer message on readers' attention, or to justify the cost to me of preparing one containing minute detail. I was doing some housekeeping in preparation for upgrading a primary authoritative nameserver currently running BIND9.18 on Ubuntu 22.04 to BIND9.20 on Ubuntu 24.04. All of the zone and key data in the directory tree */etc/bind/dynamic/* were relocated to */var/lib/bind/dynamic/* while **named** was stopped. Corresponding changes were made to the configuration. On restarting **named**, log messages seemed to indicate success, but information displayed in response to `rndc zonestatus` referred to files in */etc/bind/dynamic/*, which actually no longer existed. Specifically, after **named** had logged the message `zone foo.ie/IN: loaded serial 2022031967 (DNSSEC signed)`, indicating that the zone must have been loaded from a file in */var/lib/bind/dynamic/foo.ie/* (as this was the only available source), the response to `rndc zonestatus` included the line `files: /etc/bind/dynamic/foo.ie/db.foo.ie`. As I did not understand the significance of this anomaly, it seemed prudent to revert to the prior configuration. Thanks in anticipation, Niall O'Reilly
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
