A few days ago I changed the logs to Use Local Time on Technitium DNS Server 6.3 so I could better automate log parsing. Since then, at UTC 0 every day, the log goes haywire. EVERY single log entry as of 19:00 local time (UTC-5) requires the log to close and reopen.
You can see how this happens at exactly 19:00 in the log excerpt below, even several times per second. At first I thought it was just a one-off, but it's done this all three days now at exactly 19:00. At midnight/24:00, when the log rotates to the next date, the Stopped/Started insanity ends and it just opens the log once, until 19:00 that day.
The problem persists after restarting the service.
Disabling Use Local Time does revert to the original behavior where the log is only opened/closed on service restart.
A few days ago I changed the logs to
Use Local Time
on Technitium DNS Server 6.3 so I could better automate log parsing. Since then, at UTC 0 every day, the log goes haywire. EVERY single log entry as of 19:00 local time (UTC-5) requires the log to close and reopen.You can see how this happens at exactly 19:00 in the log excerpt below, even several times per second. At first I thought it was just a one-off, but it's done this all three days now at exactly 19:00. At midnight/24:00, when the log rotates to the next date, the Stopped/Started insanity ends and it just opens the log once, until 19:00 that day.
The problem persists after restarting the service.
Disabling
Use Local Time
does revert to the original behavior where the log is only opened/closed on service restart.