Re: defines ip to acl

2016-10-17 Thread Pol Hallen
And don't forget the copious comments in named.conf, so that your successor can easily see, at a glance, what start/end addresses those clusters of ACL elements represent. sure! :-) thanks Pol ___ Please visit https://lists.isc.org/mailman/listinf

RE: defines ip to acl

2016-10-17 Thread Darcy Kevin (FCA)
ssage- From: Darcy Kevin (FCA) Sent: Monday, October 17, 2016 3:11 PM To: bind-users@lists.isc.org Subject: RE: defines ip to acl Well, things are messy, because you haven't carved up your subnet on bit-boundaries. BIND ACLs are either individual IPs, CIDR blocks, negations, or some comb

Re: defines ip to acl

2016-10-17 Thread Pol Hallen
Acls don’t support ranges, only prefixes. You don’t want the whole /24. I think you want: acl net1 {192.168.1.0/26; 192.168.1.64/27; 192.168.1.96/30; } acl net2 {192.168.1.100/30; 192.168.104/29; 192.168.1.112/28; 192.168.1.128/26; 192.168.1.192/29; } thanks guys :-) _

RE: defines ip to acl

2016-10-17 Thread Darcy Kevin (FCA)
Well, things are messy, because you haven't carved up your subnet on bit-boundaries. BIND ACLs are either individual IPs, CIDR blocks, negations, or some combination of these. It can be done: 192.168.1.1 through 192.168.1.99 = !192.168.1.0; 192.168.1.0/26; 192.168.1.64/27; 192.168.1.96/30; 192

Re: defines ip to acl

2016-10-17 Thread McDonald, Daniel (Dan)
Acls don’t support ranges, only prefixes. You don’t want the whole /24. I think you want: acl net1 {192.168.1.0/26; 192.168.1.64/27; 192.168.1.96/30; } acl net2 {192.168.1.100/30; 192.168.104/29; 192.168.1.112/28; 192.168.1.128/26; 192.168.1.192/29; } On 2016-10-17, 13:41, "bind-users on be