I still can't reproduce this, but tracing through the code, I found two
different problems which might have a bearing. I just pushed the fixes
to these to git, and tagged 2.80test1
The fixes (top two at
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=summary) should apply
to 2.76, if that's the e
On 07/04/18 14:47, Fred Douglas wrote:
> Thanks for the explanation of REFUSED's meaning! I bet it's that the UDP
> sends are outright failing; I suspect that something is going wrong with the
> bind at program start. I'll take a look at the logs and report back on Monday.
When using port-random
Just tried a simple test, and didn't see the same behaviour.
Use log-queries to check that the process is really failing in dnsmasq,
ie the problem is not REFUSED answers from upstream. A REFUSED answer
from dnsmasq only occurs if either there are no possible upstream server
to forward to, or if
