Groups > comp.protocols.dns.bind > #15976

Re: scripts-to-block-domains

From	Grant Taylor <gtaylor@tnetconsulting.net>
Newsgroups	comp.protocols.dns.bind
Subject	Re: scripts-to-block-domains
Date	2020-07-13 13:44 -0600
Message-ID	<mailman.703.1594669450.942.bind-users@lists.isc.org> (permalink)
References	<117301d658e1$0f6966a0$2e3c33e0$@cyberia.net.sa> <7f14c6fc-804e-bca2-96f0-eb4c71d088e1@tnetconsulting.net>

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 7/13/20 12:44 AM, MEjaz wrote:
> Hell  all,

Hi,

> I have an requirement from our  national Cyber security to block several 
> thousand forged domains from our recursive servers, Is there any way we 
> can add clause in named.conf to scan such bogus domain list without 
> impacting the performance of the servers.

$RPZ++

If you can't use RPZ, then you /can/ create skeleton zones to make your 
server authoritative for the zones in question.  However, there are 
drawbacks to this regarding performance based on the number and size of 
all the additional zones.

I would strongly recommend RPZ, or the new Response Policy Service, 
which there are a few commercial implementations of.  RPS is for DNS 
what milters are for mail servers.

   RPZ is a ""static list.
   RPS is an active / dynamic service.

Note:  Response Policy Zones can be updated via normal dynamic DNS methods.

-- 
Grant. . . .
unix || die

Back to comp.protocols.dns.bind | Previous | Next | Find similar

Thread

Re: scripts-to-block-domains Grant Taylor <gtaylor@tnetconsulting.net> - 2020-07-13 13:44 -0600

csiph-web