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 'ns2.example.net'
(its IP address is 101.1.2.1), then if I put the 'also-notify {
22.22.22.222; 22.22.22.223; 22.22.22.224; };' in the zone clause, when
the zone file is modified, notify messages will be sen to 101.1.1.1,
101.1.2.1, 2.22.22.222, 22.22.22.223, and 22.22.22.224 right?
--
Bryan S.G.
On Thu, Aug 30, 2012 at 9:42 AM, Doug Barton <do...@dougbarton.us> wrote:
> 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 solution for. I used to build my conf files with m4 to work
> around this, but that was a big hammer for a very large installation.
> You might be able to do something simpler by putting notes in the conf
> to remind people who update 1 area to also update the other.
>
> Doug
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
