Unbound TCP buffer settings not sticky
-
I mean maybe wagonza can make it regen config on service restart would seem clearer. It has nothing to do with starting dnsmasq it just it shares the page with DNS Forwarder and is
Only gonna happen in pfSense2.2.
-
I mean maybe wagonza can make it regen config on service restart would seem clearer. It has nothing to do with starting dnsmasq it just it shares the page with DNS Forwarder and is
Only gonna happen in pfSense2.2.
:) fair enough as it is getting integrated in.
-
Well I reinstalled unbound again @ 4AM. Ran fine initially so I tried the option command "outgoing-range: 900" and it killed the service. I thought Wagonza put this into the pkg. I removed that and normal function returned.
So I went back to bed until later this morning. Complaints of *.org, *.info and *.co resolution started rolling in around 9AM. Narrowed it down to the incoming/outgoing buffers. When set to zero, .com, .net resolves but the others mentioned above do not. So it appears these two parameters may not be doing what they're suppose to do, or doing more than is apparent in the GUI. Suppose to ignore TCP and only use UDP.
Doesn't make sense to me that with UDP only that DNS resolution would be selective by domain.
-
@markn62 was this problem fixed for you? or is it still an issue?
Not much has changed. Seems that the package operates very much like it did since the question above was asked. The only change I noticed was a few more "do not's" that are important to adhere too for the package to work properly. I guess it is what it is.
-
@markn62 was this problem fixed for you? or is it still an issue?
Not much has changed. Seems that the package operates very much like it did since the question above was asked. The only change I noticed was a few more "do not's" that are important to adhere too for the package to work properly. I guess it is what it is.
I can't reproduce any of your current issues at all with the package even using all your custom options. Something else must be going on or you have something else as an additional problem. Try saving your whole pfsense configuration and loading that config onto a VM ands testing to give us information to go on. Or even for yourself. The devs are replacing dnsmasq with unbound afterall. If you copy your unbound.conf on your seperate box to your pfsense and only restart the service does it work?