DSNBL error: connect: Can't assign requested address for 127.0.0.1 port 953
-
Already have log level at 2, do I need to go higher?
Looks like it is resolving??
-
Still trying figure this out. Unbound is stopping and starting all the time per the logs. Still have forwarder off and no DNS servers in general setup. Pfblocker is turned off. DNS resolver status blank and dnslookup doesn't resolve anything? Is my boxed just messed up or is there issue with unbound or how do I fix this?
-
https://forum.netgate.com/topic/104772/unbound-restarting
https://forum.netgate.com/topic/138449/unbound-restarting-more-frequentlyAlso if you use the Service Watchdog package make sure it does not monitor unbound.
-
@BBcan177 fixed my issue which was unrelated to pfblocker. Somehow my Pfsense became corrupted related to the unbound_control.key and unbound_server.pem. He got it to generate new ones that fixed unbound which in turn got Pfblocker working. We are not sure why it happened but he is reporting issues to them. Owe him for sure, great guy.
-
@SnowmanUT said in DSNBL error: connect: Can't assign requested address for 127.0.0.1 port 953:
@BBcan177 fixed my issue which was unrelated to pfblocker. Somehow my Pfsense became corrupted related to the unbound_control.key and unbound_server.pem. He got it to generate new ones that fixed unbound which in turn got Pfblocker working. We are not sure why it happened but he is reporting issues to them. Owe him for sure, great guy.
Can you please post how you were able to get it to generate new unbound_control.key and unbound_server.pem? Mine seems to have the same issue, and it doesn't resolve itself when I restore older known working configs.
-
lol I have the same thing happening as well..
-
@BBcan177 helped me fix it through some remote support. Not sure of the exact commands he ran on the console to fix it. If he sees this post maybe he can provide them.
-
Hope he sees it.. I can't figure this out
-
@SnowmanUT said in DSNBL error: connect: Can't assign requested address for 127.0.0.1 port 953:
unbound_control.key
Guys why don't you use the search "unbound_control.key" feature of the forum ?
https://forum.netgate.com/topic/106011/solved-pfblockerng-reloading-unbound-fails/12
Basically remove the cert files, restart unbound or reboot.
-
@RonpfS I did exactly that.. removed keys firstly... didn't work.. renamed /var/unbound to unbound.bak.. restarted same thing.. very stange
-
fixed.. would not work on just restarting DNS.. had to reboot the box.
-
@freebs
Maybe save DNS Resolver settings then Apply settings would do the trick.
