Re: Can't transfer RFC2317 reverse zone

> With the "file" statement in the zone declaration for that zone. > > Zone "0/27.146.68.12.in-addr.arpa" { >        ... >        file "blah-blah"; > # or    file "0.27.146.68.12.in-addr.arpa";  as I believe Mark Andrews > suggested >        ... > }; > > (See also Jeff Lightner's example earlier i

Re: Can't transfer RFC2317 reverse zone

>> Nope, no such file exists.  I've got bak.* for all my other zones, but >> not that one. > > The filename you use to *save* the zone file as is arbitrary, try > blah-blah How do I specify that? ___ bind-users mailing list bind-users@lists.isc.org

Re: Can't transfer RFC2317 reverse zone

>> From what I have seen on this list, BIND typically spits out this >> error when it doesn't have write permission on its working directory. > >        No.  Read the error message.  It says "file not found" in >        this case the file not found was the directory "bak.0". > >> However, I know th

Can't transfer RFC2317 reverse zone

I'm trying to setup a new server as a slave to our master DNS server. I am able to transfer several zones just fine, but when will not transfer. AT&T uses RFC2317-style zones for reverse delegation, so I've been delegated 0/27.146.68.12.in-addr.arpa. However, when I fired up BIND and tried to tra