MIME-Version: 1.0 In-Reply-To: X-Mailer: MIME-tools 5.505 (Entity 5.505) Content-Disposition: inline X-RT-Interface: Web References: <317307465.487433.1489162746275.JavaMail.zimbra@redhat.com> <960257277.509834.1489165546786.JavaMail.zimbra@redhat.com> <20170310174641.GB92236@isc.org> <1dee09e0-c1a7-3d7f-0c71-9368e04ae1be@redhat.com> Content-Type: text/plain; charset="utf-8" Message-ID: Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 RT-Send-CC: X-RT-Encrypt: 0 X-RT-Sign: 0 Content-Length: 958 > I think there are only dynamic zones with their journal. But they use > temporary files in the same directory as themselves, aren't they? > What other problems can it make? I can think only automatic DNSSEC > resigning. Such zones are updated using dynamic updates anyway, aren't > they? Selinux will log any access violation. The only problem reported > by users was .nzf files. If you know any potential problems, I would > really like to hear them. The most significant problem that's hard to correct with careful configuration of named is that most platforms write core dumps to the working directory by default, and changing that is usually a system-wide setting rather than something that can be corrected specifically for named. It makes for difficult debugging. But I do think you're correct that the files named has direct control over can be configured to write elsewhere (with the exception of NZF and NZDB files, which your patch addresses).