• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved error writing NTA file for view '_bind'

FredFoster

New Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
Last version of Plesk
Hi Everyone

A couple of days ago, I upgraded my OS version from Debian 9 to 10. Since then, I have been facing a problem with the bind installation

I’ve got theses two messages errors in the bind.service status :
”……
error writing NTA file for view '_default': permission denied
error writing NTA file for view '_bind': permission denied
…..”

I really don’t which file might be related

I really appreciate any help

Thanks

Freddy
 
Looks like something is wrong with /var/named directory permissions. Check it with

Code:
# stat /var/named
  File: /var/named
  Size: 22              Blocks: 0          IO Block: 4096   directory
Device: 801h/2049d      Inode: 23116614    Links: 3
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)

# ls -la /var/named/
# ls -la /var/named/run-root/
 
Maybe too late for the topic starter, but seems reasonable for those who will face the problem on dist-upgrade.
I’ve had the same problem as described in the original post and the problem was in Apparmor.
Just check /var/log/messages file for errors.
AppArmor is installed and enabled by default in Debian 10.
So, I just added
/var/named/* rw,
into /etc/apparmor.d/local/usr.sbin.named and the problem gone.
 
Back
Top