Abour RRL and Best Practise

2020-11-26 Thread Onur GURSOY
Hello Everyone,

Bind9 is a good product and benchmark.
It has good documentation especially about vulnerabilities.
I wonder one thing, nowadays,

For brute force, reflection, ampliciation and etc. attacks, there is
prevention which is name response rate limit (RRL).
Question:
What is the default value rate-limit ?
What is the best practise, best value for rate-limit clause .

Thanks in advance.
Have nice day and healthy day,
With best regards

-- 
Onur GÜRSOY
R Engineer in Embedded Systems
Master Student at Gebze Institute Of Technology
Department Of Electronic Engineering
GSM : 0(545) 764 7653
e-mail: onurgursoyg...@gmail.com
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


RHEL, Centos, Fedora rpm 9.16.9

2020-11-26 Thread Carl Byington via bind-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

https://www.five-ten-sg.com/mapper/bind contains links to the source
rpms, and build instructions.


-BEGIN PGP SIGNATURE-

iHMEAREKADMWIQSuFMepaSkjWnTxQ5QvqPuaKVMWwQUCX8APLhUcY2FybEBmaXZl
LXRlbi1zZy5jb20ACgkQL6j7milTFsEA5gCfSJPL0ftRp+JlrMN4ppqBjWuyRV0A
n18rY/9MAnQikEpvgEcfj3tbiP/M
=dx29
-END PGP SIGNATURE-


___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users


Re: Two copies of recent posts

2020-11-26 Thread Matus UHLAR - fantomas

On 26.11.20 13:01, Mark Andrews wrote:

The message that generated this thread had the following:

To: upendra.gan...@gmail.com
Cc: bind-users , BIND Users 


I have mentioned this 3 days ago, this info apparently got missed.
https://lists.isc.org/pipermail/bind-users/2020-November/103912.html


Note the 2 different addresses for bind-users.  Both where delivered to
lists.isc.org in a single SMTP transaction as you noted (ESMTP id
026B967ED73) because the MTA worked out they both needed to be delivered
to the same server.  They where then sent through 2 different instances
mailman.  One for bind-users@lists.isc.org and one for bind-us...@isc.org
and re-injected (ESMTP id B380C67F367 and ESMTP id E414B67F36E).


2 mailman instaces or 2 mails to mailman, thus to the list?

This is not the first time it happened, it happed to me iirc already, when
ISC changed to mailman:

https://lists.isc.org/pipermail/bind-announce/2008-November/000570.html

maybe ISC could stop accepting the mails to old addresses?


On 26 Nov 2020, at 12:35, Paul Kosinski via bind-users 
 wrote:

Yes indeed: I sent the last email (and this one) to bind-users and CC-ed
to you.  That explains why there are two different ESMTP IDs.

The question is, have you, like I have, received two copies of any emails
(from lists.isc.org) where there *identical* ESMTP IDs in their
associated sequences of "Received:" headers.  This would indicate that
the duplication was caused by an intermediate MTA.  (The one I previously
indicated was mx.pao1.isc.org, which is the one and only MX for
lists.isc.org.)


--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Boost your system's speed by 500% - DEL C:\WINDOWS\*.*
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users