Re: Can't transfer RFC2317 reverse zone

2009-07-31 Thread Steve Brown
> 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

2009-07-31 Thread Ben Bridges
ightner's example earlier in this thread.) > -Original Message- > From: bind-users-boun...@lists.isc.org > [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Steve Brown > Sent: Friday, July 31, 2009 1:22 PM > To: bind-users@lists.isc.org > Subject: Re: Can&#x

Re: Can't transfer RFC2317 reverse zone

2009-07-31 Thread Steve Brown
>> 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

2009-07-31 Thread Rick Dicaire
On Fri, Jul 31, 2009 at 1:16 PM, Steve Brown wrote: >>        I suspect you have 'file "bak.0/27.146.68.12.in-addr.arpa";' >>        in your zone declaration.  You can't alway use the zone name >>        as a file name as a zone name may contain "/" which is a > Nope, no such file exists.  I've go

Re: Can't transfer RFC2317 reverse zone

2009-07-31 Thread Steve Brown
>> 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

RE: Can't transfer RFC2317 reverse zone

2009-07-31 Thread Jeff Lightner
What I did for our reverse zones due to the AT&T way of delegating was create two entries like this: # Special notation required for internet delegation (e.g. dig -x ...) # zone "49-62.65.210.63.IN-ADDR.ARPA" { type master; file "arpa.63.210.65"; allow-query { any; }; }; #

Re: Can't transfer RFC2317 reverse zone

2009-07-31 Thread Mark Andrews
In message <1f4ef0970907310934p2916336fy1f91485f8c17a...@mail.gmail.com>, Steve Brown writes: > 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 delegatio