Re: using acls in also-notify doesn't work -- alternative?

On Tue, Nov 09, 2004 at 08:21:13PM -0400, Danny Mayer wrote:
> At 06:18 PM 11/4/2004, Phil Dibowitz wrote:
> >So we have a little over 100 zones. Each of which has an identical
> >"also-notify" line. This is because if you define an acl and put that in
> >the
> >also-nofity line it errors:
> > Nov 4 21:59:51 kaus.usc.edu in.named[6652]: [ID 866145 daemon.error]
> > /etc/named.conf:267: expected IP address near 'notifies'
> >
> >Is there an alternative way to do this, rather than having to update 104
> >lines
> >when we need to update that list? Not that that can't be script in your
> >favorite editor, but still...
>
> Can you back up and explain why you think you need also-notify?
> If the nameserver is listed in a NS record in the zone it will always
> be notified if the zone changes whether or not you have an also-notify.
> If they are not in the list of NS records why do you think you need to
> transfer zones to them?
I have NS records for all our external facing DNS servers. We also have a
handful of DNS servers that we don't want NS records for such as servers that
have a DNS server for themselves so they don't rely on anyone else... and a
handful of other recursive servers.

--
Phil Dibowitz
Systems Architect and Administrator
Enterprise Infrastructure / ISD / USC
UCC 174 - 213-821-5427


-- Attached file included as plaintext by Ecartis --

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFBkYhO7lkZ1Iyv898RArCZAJ9VlcjdJnckz+GBwSYLAO zuxximFwCff8G5
OJN04tqzOljv83LZ5vmNZ/0=
=2rkA
-----END PGP SIGNATURE-----