Re: named.conf Default Location?

Tim, I too prefer to run BIND on FreeBSD boxes. I am running 9.10.3-P2 from ports and named.conf can only be found in: /use/local/etc/named/ Not know the exact history of your boxes, I would say it is not needed. John Sent from Nine From: Tim Daneliuk Sent: Jan 12

named.conf Default Location?

I have two FreeBSD 10 machines on which I have installed the bind99 port. The manpage for named on machine 1 says that it looks for the named.conf by default in /usr/local/etc/namedb. Machine 2's manpage says it looks in /etc/namedb. Which is correct? Is the /etc/namedb symlink even needed a

Re: Mitigation of server's load by queries for non-existing domains

Hi Tomas On Tue, Jan 12, 2016 at 05:53:20PM +0100, Tomas Hozza wrote: > Hello all. > > Recently I was trying to find a mechanism in BIND that could prevent > the server from processing a recursive query for non-existing > domains. The issue I was trying to solve was that when server was > getting

Re: Mitigation of server's load by queries for non-existing domains

Tomas Hozza wrote: > > Recently I was trying to find a mechanism in BIND that could prevent the > server from processing a recursive query for non-existing domains. Have a look at https://www.isc.org/blogs/tldr-resolver-ddos-mitigation/ > I was thinking about using RPZ with QNAME policy trigger,

Mitigation of server's load by queries for non-existing domains

Hello all. Recently I was trying to find a mechanism in BIND that could prevent the server from processing a recursive query for non-existing domains. The issue I was trying to solve was that when server was getting too many queries for such domains it was not able to handle other relevant quer