Hi both.
You can't do it using ACLs. But you can do it using primaries. This is
hinted at in the section about the primaries statement, but not clearly
expanded on.
For example:
# define a primaries list called "also-notifed" (or anything you like).
Define as many lists as you need.
primaries also
Randy,
ra...@psg.com (Randy Bush) wrote:
> can i use an acl{} or other macro in `also-notify`? i have a bunch of
> zones where i want the same `also-notify` list.
Been running into the same issue and tried to find out. My master lists and acls
are identical as yours seem to be. I've been told t
On 11/10/2021 6:25 AM, Giddings, Bret wrote:
Is there any other facility for including effectively the same grant
statements within multiple zones?
I am not aware of any
--
Do things because you should, not just because you can.
John Thurston907-465-8591
john.thurs...@alaska.gov
Departm
On 8 October 2016 at 09:57, Pol Hallen wrote:
> 192.168.1/24 is not a valid netmask
>>
>
> huh?
> In linux and BSD I always use 192.168.1/24 (how shortcut of 192.168.1.0/24)
> and so on...
You're confusing network configuration with ACL syntax.
Where you're using 192.168.1.50/24 in your OS con
I think what you are looking for is:
acl test0 { !192.168.1.50/32; 192.168.1.0/24; };
http://jodies.de/ipcalc is a good resource for checking. (As was mentioned
by Reindl...)
Learning basic sub-netting of IP addresses (Both IPv4 and IPv6) takes time
but it's necessary for DNS configuration. Ther
On 8 October 2016 at 14:14, Pol Hallen wrote:
> acl test0 { !192.168.1.50/24; 192.168.1/24;};
acl test0 { !192.168.1.50; 192.168.1.0/24;};
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mail
Am 08.10.2016 um 16:57 schrieb Pol Hallen:
192.168.1/24 is not a valid netmask
huh?
In linux and BSD I always use 192.168.1/24 (how shortcut of
192.168.1.0/24) and so on...
hint: using /24 everywhere is nonsense
why?
My goal is allow 192.168.1.0/24 (net) and deny 192.168.1.50 (host)
be
192.168.1/24 is not a valid netmask
huh?
In linux and BSD I always use 192.168.1/24 (how shortcut of
192.168.1.0/24) and so on...
hint: using /24 everywhere is nonsense
why?
My goal is allow 192.168.1.0/24 (net) and deny 192.168.1.50 (host)
thanks
Pol
___
Am 08.10.2016 um 15:14 schrieb Pol Hallen:
Hi all :-)
can someone advice me about a fully howto / handbook to understand ACL?
I need to permit all network 192.168.1/24 and deny 192.168.1.50/24 host:
acl test0 { !192.168.1.50/24; 192.168.1/24;};
192.168.1/24 is not a valid netmask
192.168.1
> I'm not very familiar with the concept of views but I wonder if the
> "match-client" statement might be the way to go.
It sounds like the one you're interested in is "match-destinations"
actually.
options {
listen-on port 53 { 128.83.185.40; 128.83.185.41; ; };
...
};
clients that I am serving don't have direct access to the authoritative
servers.
Prabhat.
--- On Mon, 7/12/10, Nuno Paquete wrote:
From: Nuno Paquete
Subject: Re: ACL for forward zone
To: "Prabhat Rana"
Cc: bind-users@lists.isc.org
Date: Monday, July 12, 2010, 4:17 PM
Hi Nuno,
Thanks for the response. However, I don't own the authoritative servers. And
the clients that I am serving don't have direct access to the authoritative
servers.
Prabhat.
--- On Mon, 7/12/10, Nuno Paquete wrote:
> From: Nuno Paquete
> Subject: Re: ACL for f
Hi Prabhat,
I think you don't need this ACL in your forwarder server, define it on
the authoritative server (1.2.3.4 and 5.6.7.8, according to your
example).
Regards,
Nuno Paquete
No dia 2010/07/12, às 19:27, "Prabhat Rana"
escreveu:
Hello all,
I have BIND 9.7.1 installed in Solaris
On Mar 23 2009, John D. Vo wrote:
Trying to implement acl in my named.conf... for Bind 9.2.2
acl eagle { 192.168.1.0/24; localhost; };
But when I issued an reload, I got:
Mar 23 08:55:39 ns1 named[13578]: [ID 866145 daemon.error]
/etc/named.conf:2: unknown option 'acl'
Mar 23 08:55:39 ns1 na
In message <49c79d6b.7060...@eagle.net>, "John D. Vo" writes:
> Greetings:
>
> Trying to implement acl in my named.conf... for Bind 9.2.2
>
> acl eagle { 192.168.1.0/24; localhost; };
>
> But when I issued an reload, I got:
>
> Mar 23 08:55:39 ns1 named[13578]: [ID 866145 daemon.error]
> /etc
Worked like a charm.
Thanks.
-John
Alan Clegg wrote:
John D. Vo wrote:
Greetings:
Trying to implement acl in my named.conf... for Bind 9.2.2
acl eagle { 192.168.1.0/24; localhost; };
But when I issued an reload, I got:
Mar 23 08:55:39 ns1 named[13578]: [ID 866145 daemon.erro
On Tue, Jan 20, 2009 at 12:24:37PM +0100,
GanGan wrote
a message of 20 lines which said:
> how to make a bind that reponde DNS fields with which he's the
> master ?
List the zones for which it is a master in named.conf.
> and it doesnt meet the request of the domain from which there is no ma
17 matches
Mail list logo
