Can't transfer RFC2317 reverse zone

[Mark Andrews]

In message <1f4ef0970907310934p2916336fy1f91485f8c17a771 at 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 delegation, so
> I've been delegated 0/27.146.68.12.in-addr.arpa.  However, when I
> fired up BIND and tried to transfer the zone from the master, I get
> this in the logs:
> 
> 30-Jul-2009 13:18:37.094 zone
> 0/27.146.68.12.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public:
> Transfer started.
> 30-Jul-2009 13:18:37.096 transfer of
> '0/27.146.68.12.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public' from
> 12.68.146.1#53: connected using 206.123.100.18#52732
> 30-Jul-2009 13:18:37.100 dumping master file: bak.0/tmp-Yj75Mq2ImU:
> open: file not found
> 30-Jul-2009 13:18:37.100 transfer of
> '0/27.146.68.12.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public' from
> 12.68.146.1#53: failed while receiving responses: file not found
> 30-Jul-2009 13:18:37.100 transfer of
> '0/27.146.68.12.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public' from
> 12.68.146.1#53: end of transfer
> 
> 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 this is not the case because it transferred a dozen
> other zones just fine. Its only barfing on this one reverse zone. I'm
> guessing that it has something to do with how BIND names the temp
> files it creates for writing slave zones, combined with the fact that
> there is a "/" (forward slash) in the name it would like to write?
> I've been searching for a way to specify the name of the temp file
> BIND uses, but I've had no luck finding that.

	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 
	directory seperator in a file name.  Now you could use
	'file "bak.0.27.146.68.12.in-addr.arpa";'  or you could
	create the directory "bak.0".  I would choose the former.

	Mark

> Any thoughts or ideas on how I can get this slave zone to transfer correctly?
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org