Hi,
First post here!
At my current occupation we rely heavily on our internal DNS operating
correctly.
And I got involved on how we would do change management, or specifically
unit test our existing configuration.
I got interested and started a personal project of mine, currently named
bsa for
I tried to use the acl statement in my named.conf file, but I have a
hard time making it work. In my named.conf file, I've put these acl
statements in these formats (made up IP addresses mind you):-
--
// Individual ACL list
acl addr1 {
11.22.33.44;
12.23.34.45;
};
acl
On 08/29/2012 03:25 PM, GS Bryan wrote:
Then when I put the 'alladdr' thing in my 'allow-transfer' and
'also-notify' arguments,
also-notify does not take an acl. The ARM will give you more information
on the grammar.
That said, this is a very annoying problem that I wish there was a
better
On Thu, 30 Aug 2012, GS Bryan wrote:
also-notify { alladdr; };
This uses an ip_addr instead of an address_match_list. Some versions of
named-checkconf will tell you expected IP address.
/etc/named.conf:111: masters alladdr not found
I can't reproduce your problem. What version of
In message
CAOJ-cLgi-Z1DyEnKq1PbK4+jzGG3ew8ZHfv10B751sEbb9V-=q...@mail.gmail.com
, GS Bryan writes:
I tried to use the acl statement in my named.conf file, but I have a
hard time making it work. In my named.conf file, I've put these acl
statements in these formats (made up IP addresses mind
Hi Mark,
Thanks for the heads up; I have tested this patch in our environment and it
fixes the problem for us :).
As we have Red Hat support, I have asked if they would include this patch early
for us.
In the meantime, I'm considering just running a hand compiled version of
'named-checkconf'
On 08/29/2012 04:02 PM, Mark Andrews wrote:
A plain address in a acl is shorthand for address/32 or address/128
depending apon the address type. While they are visually similar
the two list are functionally very different.
Mark,
I understand the behind the scenes reasons why the 2 things are
hmm... that explains it.
Damn, DNSMadeEasy needs to have notify notices sent to a different IP
set than their nameserver service. This means that I have to hardcode
this myself.
Another question then, if zone 'example.net' has the NS records of
'ns1.example.net' (its IP address is 101.1.1.1) and
My BIND version, as shown by 'named -v' is BIND 9.9.1-P1-RedHat-9.9.1-2.P1.el6.
'named-checkconf /etc/named.conf' doesn't throw any error messages whatsoever.
--
Bryan S.G.
On Thu, Aug 30, 2012 at 9:59 AM, Jeremy C. Reed jr...@isc.org wrote:
On Thu, 30 Aug 2012, GS Bryan wrote:
9 matches
Mail list logo
