Actions
Bug #13772
open
Changing the alias resolve interval to the default value does not take effect after saving.
Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Aliases / Tables
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.0
Affected Architecture:
Description
Under System / Advanced / Firewall & NAT, if the Aliases Hostnames Resolve Interval option is changed from a custom value to a blank (default) value, filterdns processes are not restarted. Changes to custom values do correctly restart the processes.
Updated by Danilo Zrenjanin over 2 years ago
- Status changed from New to Confirmed
In my tests, even when I changed to a custom value, I had to "Reload Filter" to get it to run with the newly defined time interval.
Actions