(04-07-2019, 05:21 PM)fearworks Wrote: All of my permissions are the same as the OP's. Even my Sentora folder is root:root, so I'm guessing that CentOS have changed things since Sentora's 2015 release? I've not had permissions issues with anything so for me this has always been the setup and it has been working without issue.
As for the error message, I also have those lines in my bind logs, and they are to do with the service being stopped (including when restarted). If you look here:
https://bugzilla.redhat.com/show_bug.cgi?id=1487823
you will see a discussion about the issue, which is linked to permissions on the named home directory. AFAIK the inability to write these NTA files is irrelevant to the way bind is used by Sentora so TBH, I don't care about the entries. However if we want to fix this I have just tried:
Code:chmod 775 /var/named/
and now whenever I restart the named service those errors aren't being generated.
So, in summary, there's some sort of bug in the release of bind used by CentOS 7 (and maybe others?) that seems to alter the permissions of the directory in question upon installation, and we have to change these permissions back to allow writing.
That's my assessment of the situation, but as I'm not an expert I could be completely wrong, so if you think I am - tell me!
Keith.
Hi all forgive me for the late response.
I changed the named to chmod 755 as you said and restarted the service and seems that no more erros writting nta files appeared
Despite there is no errors in the bid log, when i try to nagivate to the url of my domain i still got dns error like this
and still no idea what error could be