---
title: "transfer of 'example.net/IN' failed errors"
slug: "aa-00301"
description: "These indicate a filesystem permission error preventing named from creating / renaming the temporary file."
updated: 2018-10-26T16:51:04Z
published: 2018-10-26T16:51:05Z
canonical: "kb.isc.org/aa-00301"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.isc.org/llms.txt
> Use this file to discover all available pages before exploring further.

# I get "transfer of 'example.net/IN' from 192.168.4.12#53: failed while receiving responses: permission denied" error messages.

These indicate a filesystem permission error preventing **named** from creating / renaming the temporary file. These will usually also have other associated error messages like:

```
"dumping master file: sl/tmp-XXXX5il3sQ: open: permission denied"
```

**named** needs write permission on the directory containing the file. **named** writes the new cache file to a temporary file, then renames it to the name specified in `named.conf`to ensure that the contents are always complete. This is to prevent **named** loading a partial zone in the event of power failure or similar interruption of the write of the master file.

Note file names are relative to the directory specified in options and any chroot directory ([<chroot dir>/][<options dir>]).

If **named** is invoked as "named -t /chroot/DNS" with the following `named.conf`, then "/chroot/DNS/var/named/sl" needs to be writable by the user **named** is running as.

```
options { directory "/var/named";};zone "example.net" { type slave; file "sl/example.net"; masters { 192.168.4.12; };};
```