Filterdns has stopped resolving hostnames in firewall aliases

SteveITS

I ran into a problem today where our office pfSense did not have the correct IP for a hostname in an alias.

Per the DNS Resolver log the last filterdns entry was March 20. There are no filterdns entries in the system log.

The "Unable to create monitoring thread" error is NOT being logged.

All the expected filterdns processes ARE running [per Diagnostics> System Activity], for each hostname:

20    0   111M    20M usem     2   0:09   0.00% /usr/local/sbin/filterdns -p /var/run/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1{example.net}
16827 root

Before I start restarting things, any idea where to look as to why it isn't resolving hostnames after March 20?

SteveITS

Sounds like https://redmine.pfsense.org/issues/8758 in particular the "Is" state:

root    62658   0.0  0.5 113276  20412  -  Is    4Feb25      1:59.64 /usr/local/sbin/filterdns -p /var/run/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1

Similar to that one, if I "killall filterdns" and then Status>Filter Reload, the table is immediately updated. (for convenience "pfctl -T show -t aliasname" shows this at a command prompt)

FWIW that redmine links to https://redmine.pfsense.org/issues/9296
...but both are marked as closed/resolved. :(