Pfb_dnsbl.conf too big?
-
I currently have the problem, that my pfb_dnsbl.conf is about 700k lines long ~35MB size.
As soon as I enable it in the DNS Resolver (server:include: /var/unbound/pfb_dnsbl.conf) it wont resolve any dns entries anymore.
I tried increasing the cache size and a few other options with no success.
When I decrease the size of the conf it works, but is there any way around this limit or have I setup something wrong? -
How much memory do you have ?
-
8GB
-
I just deleted only the last line and now it works?
DNS Resolver Logs shows no errors either.
I don't know whats happening, I should go to sleep. -
You shouldn't need to edit the Unbound Adv. custom line, that is managed by the pkg.
When DNSBL downloads each feed, it does a validation to ensure there is no bad data in the parsing… So check the pfblockerng.log for any anomalies.. When all the DNSBL feeds are downloaded and parsed, it will create the new pfb_dnsbl.conf file automatically and reload that…. You shouldn't need to make any changes to it.
This will confirm if Unbound is running:
unbound-control -c /var/unbound/unbound.conf statusAlso check the pfBlockerNG Alerts tab for any blocked domains/IPs that could be causing this issue…
-
It's really odd, I get some DNS outages once in a while, but sometimes only for a few minutes, maybe during cron?
The only errors I get is:
unbound 22943:0 error: cannot chdir to directory: (No such file or directory) -
During a cron update of DNSBL it can temporarily stop DNS requests since its reloading Unbound…. Next release will have a Live Sync feature.. Just working out the bugs with it .... So try to set DNSBL to update once per night so it will minimize the impact.
Could you be affected by the following:
https://redmine.pfsense.org/issues/7326Hoping to get some resolution to that asap from the DEVS…
-
The only errors I get is:
unbound 22943:0 error: cannot chdir to directory: (No such file or directory)This "error" has been present for ages. It doesn't cause any problem as far as I know.
