9.2.1 secondary transfer
ngaccess at hotpop.com
ngaccess at hotpop.com
Tue Sep 30 18:41:09 UTC 2003
Yep - that's it !!!
They have allow-transfer { localhost; }; - so that is what's killing the
global huh ....
How/what do I change to 'kill' that when it writes a new zone so the
global will apply to tht of the 80 something domains to setup?
TIA
On 30 Sep 2003 at 18:00, Barry Margolin wrote:
To: comp-protocols-dns-bind at isc.org
From: Barry Margolin <barry.margolin at level3.com>
Subject: Re: 9.2.1 secondary transfer
Organization: Level(3) Communications, Woburn, MA
Date sent: Tue, 30 Sep 2003 18:00:37 GMT
> In article <blcg9e$2984$1 at sf1.isc.org>, <ngaccess at hotpop.com> wrote: >I
> forgot to mention that it has an ensim control panel but the only
> >difference that I see there is it refers /etc/named.conf to
> >/etc/bind/options.conf.wp which here is the contents of ... > >// This
> file stores the options statement maintained by Ensim > >options { >
> directory "/var/named"; > listen-on { 127.0.0.1; 66.227.32.153;
> 66.227.32.154; 66.227.32.158; }; > allow-transfer { localhost;
> 199.242.242.199; }; >}; > >199.242.242.199 is obviously what I want to
> transfer to ... > >Any ideas why it keeps refusing?
>
> Do the zones have their own "allow-transfer" options? If so, that
> overrides the global one.
>
> --
> Barry Margolin, barry.margolin at level3.com
> Level(3), Woburn, MA
> *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to
> newsgroups. Please DON'T copy followups to me -- I'll assume it wasn't
> posted to the group.
>
>
More information about the bind-users
mailing list