In article ,
Frank Liu wrote:
> Thanks for confirming bind behavior matches what I saw.
> I noticed other resolvers (eg: @8.8.8.8) works differently, c.b.a.com NS
> host2 actually got used, not ignored as occluded data.
On Thu, Nov 15, 2018 at 8:25 AM Barry Margolin wrote:
That shouldn't
Nikolai Lusan wrote
> On Thu, 2018-11-15 at 05:49 -0600, sethologik wrote:
>> But this is what i already did...
>>
>> could it be something with the firewall?
>
> It _could_ be many things. You need to properly troubleshoot the issue.
> 1) Can a host with failing DNS resolution ping the DNS
I have the solution.
I added another zone named only "weberver01." with one wildcard entry
* IN A x.x.99.216
Now everything is working fine and windows as well as linux have proper
answers while using nslookup, dig or in browser just like it was with
dnsmasq
Thanks for your help :-)
--
Sent
On 9/29/18, Evan Hunt wrote:
> On Sat, Sep 29, 2018 at 05:48:55PM -0400, Lee wrote:
>> Can someone tell me what can cause
>> stop on unrecognized qresult in rpz_rewrite()failed:
>> or how to fix whatever it was?
>
> It's an interaction between RPZ and aggressive negative caching (i.e.
>
On 11/16/18, Evan Hunt wrote:
> On Fri, Nov 16, 2018 at 11:44:11AM -0500, Lee wrote:
>> > It's an interaction between RPZ and aggressive negative caching (i.e.
>> > "synth-from-dnssec"). It's fixed in the upcoming release.
>>
>> I should have asked which upcoming release? It's still happening in
On Fri, Nov 16, 2018 at 11:44:11AM -0500, Lee wrote:
> > It's an interaction between RPZ and aggressive negative caching (i.e.
> > "synth-from-dnssec"). It's fixed in the upcoming release.
>
> I should have asked which upcoming release? It's still happening in 9.11.5:
I'm sorry, I should have
6 matches
Mail list logo
