Hi Simon,
> Well, that's the smoking gun. Dnsmasq is doing the right thing, and your
> upstream server at 212.202.215.1 is broken. I realise that doesn't solve
> the problem, but at least you know where to work now :)
>
>
> (the reason dnsmasq is returning SERVFAIL is that there's a
>
The mystery is at least partially solved. It looks like I'd somehow
enabled Remote Routing and Access services within Windows Home Server
for VPN access. It looks like it tries to grab a few addresses for
potential VPN clients from a DHCP server, that's why I was seeing
'RRAS.Micrsoft' as a
On 03/05/16 18:48, Kevin Darbyshire-Bryant wrote:
> Hi Simon,
>
> Thanks for getting back to me. Kermit is a Windows Home Server box and
> is definitely not net or dual booted. Here's the relevant 'log dhcp'
> extract from a clean boot of it.
>
>
Thank you!
Neil
On 03/05/16 23:28, Simon Kelley wrote:
> That seems quite straightforward. Thanks. Patch applied without change.
>
> Cheers,
>
> Simon.
>
>
>
> On 08/04/16 19:27, Neil Jerram wrote:
>> I'm sorry not to have noticed this before now, but I just spotted that
>> DHCPv4
On Tue, Apr 26, 2016 at 03:43:34PM -0700, Mike Leong wrote:
> I have a blacklist of 1.5 million entries loaded into dnsmasq via "address"
> definitions. eg:
> address="/bad-site.com/192.168.5.1"
https://github.com/infinet/dnsmasq
> The 1.5 million entries are a list of porn/warze sites
