From d17b5ab45dc7df51836e26d7a38450cd391b94b2 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Sat, 13 Jun 2026 16:59:26 +0200 Subject: [PATCH] docs: v0.29.1 lanresolver fix note in REPORT Co-Authored-By: Claude Opus 4.8 (1M context) --- REPORT.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/REPORT.md b/REPORT.md index 84aadd2..dafdfb6 100644 --- a/REPORT.md +++ b/REPORT.md @@ -1,3 +1,15 @@ +# REPORT — felhom-agent v0.29.x (OS / Docker-data storage split + lanresolver fix) + +> **Follow-up v0.29.1 (lanresolver):** the v0.29.0 re-provision moved 9201's DHCP IP (.151 → .141), but +> LAN clients kept resolving the old IP. Root cause: `lanresolver` updated the dnsmasq drop-in +> (`address=//`) then ran `systemctl reload dnsmasq` — **SIGHUP does not re-read config +> drop-ins** (only `/etc/hosts` + cache), so the changed `address=` never took effect. Fixed: +> `reload()` → `restartDnsmasq()` (`systemctl restart`). Deployed live; host dnsmasq restarted + Pi-hole +> cache flushed; `*.demo-felhom.eu` now resolves to .141 and LAN HTTPS returns 200. Future IP moves +> self-heal on the loop's next tick. (DHCP for the guest is fine — no static IP needed.) + +--- + # REPORT — felhom-agent v0.29.0 (OS / Docker-data storage split: golden + provision) Phase 1 of the storage-split slice (Phase 2 = felhom-controller v0.58.0 prevention layer). The