On 18/05/2024 09:11, J Doe wrote:
Hello,
When using RPZ with BIND 9.18.27 and rpz-ip, can any CIDR prefix be used
or must they be either: /8, /16, /24, /32 for IPv4 ?
For example, if I want to block records with an A address of
192.168.10.1, I know I can write:
32.1.10.168.192.rpz-ip
Hello,
When using RPZ with BIND 9.18.27 and rpz-ip, can any CIDR prefix be used
or must they be either: /8, /16, /24, /32 for IPv4 ?
For example, if I want to block records with an A address of
192.168.10.1, I know I can write:
32.1.10.168.192.rpz-ipINCNAME .
... and records
Correct. Later versions use NS queries as that allows named to cache the
non-existence of the NS RRset. Using _.domain doesn’t allow that to happen.
NS queries do however expose broken delegations. Make sure you have working NS
records at the zone apex and at the delegation point. This is
On Fri, May 17, 2024 at 03:25:01PM +0200,
Matus UHLAR - fantomas wrote
a message of 43 lines which said:
> I have noticed that BIND sends strange (for me) queries.
>
> 5 0.198221 192.168.0.1 → 193.108.88.128 DNS 105 Standard query 0x15a4 A
> _.net.akadns.net OPT
QNAME minimisation
Hello,
I have noticed that BIND sends strange (for me) queries.
5 0.198221 192.168.0.1 → 193.108.88.128 DNS 105 Standard query 0x15a4 A
_.net.akadns.net OPT
8 0.204738 193.108.88.128 → 192.168.0.1 DNS 159 Standard query response
0x15a4 No such name A _.net.akadns.net SOA
Hi,
On 5/16/24 14:02, adrien sipasseuth wrote:
Hello,
I try to set up a testing environment in order to create some scripts
for automated the roll over KSK.
# question 1 #
this is my policy :
dnssec-policy "test" {
keys {
ksk lifetime P3D algorithm
6 matches
Mail list logo
