"unbound mode" vs "unbound python mode"

[netboy]

I changed the mode from "unbound mode" to "unbound python mode" and all of a sudden the DNS in browser is not working! Any tips ?

[keyser]

@netboy Try and restart the Unbound service. I have seen errors where the unload/reload of of unbound took to long when changing the working method, and caused unbound to fail.

[netboy]

@keyser said in "unbound mode" vs "unbound python mode":

Try and restart the Unbound service

I did restarrt -> all no luck. Finally had to revert back to "Unbound mode".

Why is this happening - Unbound Python mode is supposed to be faster "in theory" but does not work

[keyser]

@netboy Okay, then I think it sound like you have not asked pfBlockerNG to reload and update after changing the setting to unbound python mode. As far as I remember it needs to rebuild how it interacts with Unbound when you change the setting. That is done by doing the pfBlockerNG reload (that also reloads unbound in turn).

Just to be clear - it does work - thousands and thousands of installations use that setting are running around the world. I myself have control over a hundred right now that has been running for years in “unbound python mode”. So we need to figure out why it’s not working in your setup right now.

[netboy]

@keyser said in "unbound mode" vs "unbound python mode":

Okay, then I think it sound like you have not asked pfBlockerNG to reload and update after changing the setting to unbound python mode

not true - this is exactly what i did - i did a RELOAD -> ALL -> RUN

[keyser]

@netboy Okay.. then I’m afraid I don’t exactly know what to do next.
There are lots of pfBlockerNG experts on this forum, so hopefully someone else can diagnose this quickly for you.

[netboy]

@keyser I am not an expert in pfBlockerNG as well.

My understandint is "Unbound using python" parses the dns texts and mappings in memory and and is faster! based on this "assumption" i changed to python and off course reloaded using option

reload -> all. -> run

and immeidatly all my public websites refused to load. I can only describe the symptoms

[SteveITS]

@netboy In DNS Resolver settings, is "Enable Python Module" checked?

Python mode is generally recommended as, for instance, there are many posts about kea2unbound or other types of out of memory errors.

[keyser]

@netboy I understand. A good guess since your websites (internetaccess) no longer works is that DNS stops working.
That in turn suggests that Unbound (pfSense’s built in DNS server stopped working when attempting to start with the pfBlockerNG integration engaged.

Try and check that Unbound have the python integration llisted in its config:

Next thing would be to look into the STATUS -> SYSTEM LOGS -> GENERAL/RESOLVER log and see if Unbound is spitting some usefull info into there