Hello G.W. Haywood,
Am 2011-10-27 16:56:44, hacktest Du folgendes herunter:
> On Thu, 27 Oct 2011 Michelle Konzack wrote:
> > ...and you get the hell on you ass if you have several 1000 of them!
> > In this case, bind9 with RPZ is cheaper.
> Maybe look at ipsets. Currently we firewall almost 76,0
Hi there,
On Thu, 27 Oct 2011 Michelle Konzack wrote:
> Am 2011-10-17 13:28:43, hacktest Du folgendes herunter:
>
> > ... I found that setting up iptables to do drops for known bad
> > IPs/ranges was slightly better as the traffic never gets to BIND
> > ...
> > Example rules for various IPs that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/17/2011 02:19 PM, Phil Mayers wrote:
> On 10/17/2011 06:38 PM, babu dheen wrote:
>> YOu are obsolutely correct Chris.. I want to block/redirect all malware
>> domain request intiated by clients by setting up DNS SINKHOLE in Redhat
>> BIND server.
to get it.
-Original Message-
From: bind-users-bounces+jlightner=water@lists.isc.org
[mailto:bind-users-bounces+jlightner=water@lists.isc.org] On Behalf Of
Michelle Konzack
Sent: Wednesday, October 26, 2011 9:01 PM
To: bind-users@lists.isc.org
Subject: Re: DNS Sinkhole in BIND
Hello Ligh
Hello Lightner, Jeff,
Am 2011-10-17 13:28:43, hacktest Du folgendes herunter:
> While setting up blackholes in BIND works fine when I did this on
> Linux I found that setting up iptables to do drops for known bad
> IPs/ranges was slightly better as the traffic never gets to BIND in
> the first pla
On 10/17/2011 09:05 PM, Lightner, Jeff wrote:
I’m confused – does the OP want to block or does he want to redirect.
“block/redirect” are two different things. What I wrote will block. If
It'll block IPs, and whole IPs at that. If the server is shared, you
block all traffic to it, not just the
;
>Sent: Monday, October 17, 2011 4:05 PM
>Subject: RE: DNS Sinkhole in BIND
>
>
>
>I’m confused – does the OP want to block or does he want to redirect.
>“block/redirect” are two different things. What I wrote will block. If he
>wants to redirect that’s fine but
-users-bounces+jlightner=water@lists.isc.org
[mailto:bind-users-bounces+jlightner=water@lists.isc.org] On Behalf Of Ryan
Novosielski
Sent: Monday, October 17, 2011 3:52 PM
To: babu dheen; Bind Users Mailing List; c...@cam.ac.uk
Subject: Re: DNS Sinkhole in BIND
I do this. There may now be
son <c...@cam.ac.uk> wrote:
From: Chris Thompson <c...@cam.ac.uk>
Subject: Re: DNS Sinkhole in BIND
To: "Bind Users Mailing List" <bind-users@lists.isc.org>
Cc: "babu dheen" <babudh...@yahoo.co.in>
Date: Monday, 17 October, 2011, 8:19 PM
On Oct 16 2011, babu d
On 10/17/2011 06:38 PM, babu dheen wrote:
YOu are obsolutely correct Chris.. I want to block/redirect all malware
domain request intiated by clients by setting up DNS SINKHOLE in Redhat
BIND server.
In older versions of bind, you needed to create a local zone per malware
domain (or hostname).
YOu are obsolutely correct Chris.. I want to block/redirect all malware domain
request intiated by clients by setting up DNS SINKHOLE in Redhat BIND server.
--- On Mon, 17/10/11, Chris Thompson wrote:
From: Chris Thompson
Subject: Re: DNS Sinkhole in BIND
To: "Bind Users Mailing List
On Oct 16 2011, babu dheen wrote:
Can anyone help me how to setup DNS Sinkhole in BIND on Linux 32 bit edition.
All the replies to this so far seem to assume that he wants to block evil
entities from using his nameservers. But Google seems to suggest that
"DNS Sinkhole" usually refers to redir
, Jeff
Sent: Monday, October 17, 2011 9:29 AM
To: TCPWave Customer Care; babu dheen
Cc: bind-users@lists.isc.org
Subject: RE: DNS Sinkhole in BIND
While setting up blackholes in BIND works fine when I did this on Linux I found
that setting up iptables to do drops for known bad IPs/ranges was
org
Subject: Re: DNS Sinkhole in BIND
Babu
The following example defines two access control lists and uses an
options statement to define how they are treated by the nameserver:
acl black-hats { 10.0.2.0/24; 192.168.0.0/24; };
acl red-hats { 10.0.1.0/24; };
options {
blackho
Babu
The following example defines two access control lists and uses an
options statement to define how they are treated by the nameserver:
acl black-hats { 10.0.2.0/24; 192.168.0.0/24; };
acl red-hats { 10.0.1.0/24; };
options {
blackhole { black-hats; };
allow-q
15 matches
Mail list logo
