adamandClaude Opus 5.5 33060f86ce Don't count a per-view counter going down as a restart of named ...

After a reconfig that changed named's views, the cache and resolver
counters (summed over views) went down, which was taken for a restart:
every counter then counted its total since named started for one minute.
Only a new boot time means a restart now; a counter that goes down
counts 0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-11 16:51:24 +01:00

..

blocking_test.go

Pause blocking, blocked clients and a blocked line in the statistics, compact view picker

2026-10-10 11:10:44 +00:00

collector_test.go

Mark signed zones with a padlock, and name clients in statistics

2026-10-09 23:27:53 +00:00

collector.go

Pause blocking, blocked clients and a blocked line in the statistics, compact view picker

2026-10-10 11:10:44 +00:00

inode_other.go

Split the packages, publish releases from Gitea Actions, release 0.1.0

2026-10-09 08:40:56 +00:00

inode_unix.go

Split the packages, publish releases from Gitea Actions, release 0.1.0

2026-10-09 08:40:56 +00:00

parse_test.go

Add optional query statistics

2026-10-07 20:21:34 +00:00

parse.go

Add blocking: blocklists and block/allow rules with BIND response policy zones

2026-10-10 09:24:19 +00:00

poll_test.go

Don't count a per-view counter going down as a restart of named

2026-10-11 16:51:24 +01:00

poll.go

Don't count a per-view counter going down as a restart of named

2026-10-11 16:51:24 +01:00

query.go

Add blocking: blocklists and block/allow rules with BIND response policy zones

2026-10-10 09:24:19 +00:00

store.go

Mark signed zones with a padlock, and name clients in statistics

2026-10-09 23:27:53 +00:00

tail_test.go

Add optional query statistics

2026-10-07 20:21:34 +00:00

tail.go

Split the packages, publish releases from Gitea Actions, release 0.1.0

2026-10-09 08:40:56 +00:00