9b5c2e1994
Unit Tests / test (push) Successful in 7m35s
Three related issues prevented CoreDNS from serving updated zone records: 1. The `file` plugin blocks in generate_corefile() lacked a `reload` option, so CoreDNS never re-read zone files after they were written. Added `reload 30s` so zone file changes are picked up within 30s. 2. _reload_dns_service() sent SIGHUP via `docker exec ... kill -HUP 1`, which doesn't trigger zone reloads. Changed to SIGUSR1 via `docker kill --signal=SIGUSR1` (same as firewall_manager.reload_coredns). 3. _bootstrap_dns() wrote the zone file but never regenerated the Corefile. CoreDNS's reload plugin only fires when the Corefile changes, so zone records from startup were invisible until the next peer modification triggered apply_all_dns_rules(). Now _bootstrap_dns() always calls apply_all_dns_rules() after the zone write. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>