DNS Port 53 is closed?!?

[Surf3rDud3]

Restarted my server and now the Server Status shows DNS port 53 as blocked. all my domain names besides my main one arent working showing a dns error.

I dont know what i have to do to open the port back up or if i need to restart the dns server.

Willing to compensate for your time.

[Me.B]

Check if bind is working first.

Check if anything is using that port.

M B

PS: don't double post.

[Surf3rDud3]

Tried reloading bind. I get this when using "systemctl status named.service".

Code:

Nov 29 14:02:26 cp.devrea.com named[14518]: open:
/etc/named.conf: permission denied              
Nov 29 14:02:26 cp.devrea.com named[14518]: loadi
ng configuration: permission denied              
Nov 29 14:02:26 cp.devrea.com systemd[1]: named.s
ervice: control process exited, code=exited statu
s=1                                              
Nov 29 14:02:26 cp.devrea.com systemd[1]: Failed
to start Berkeley Internet Name Domain (DNS).    
Nov 29 14:02:26 cp.devrea.com systemd[1]: Unit na
med.service entered failed state.                
Nov 29 14:02:26 cp.devrea.com systemd[1]: named.s
ervice failed.

Did permissions get messed up?

Edit: Home now able to pull more info.

Heres my bind.log, this is the error that keep repeating.

Code:

26-Nov-2016 16:30:01.820 security: warning: using built-in DLV key for view _default
26-Nov-2016 16:30:01.821 general: error: managed-keys.bind.jnl: create: permission denied
26-Nov-2016 16:30:01.821 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
26-Nov-2016 16:30:01.821 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
26-Nov-2016 16:30:01.823 general: notice: all zones loaded
26-Nov-2016 16:30:01.823 general: notice: running

Its something to do with permissions i don't know how to go about fixing. Ive looked it up and most cases people just reinstall the OS which id rather not do.

I run a Game Panel on the VPS too called TCAdmin. I was having permission problems on there as well. So I dont know if both of them running on the same VPS is a problem I've seen it work on Windows which is what I was coming from before I switched to CentOS.

If I need to split the two on different machines I will but if they shouldn't be conflicting then I'd rather have them both run on the same machine.

FIXED! Used "systemctl enable named" and chmod 775 named.conf and it worked... tried chown bind:bind etc. but it said the user didnt exist but now its working. So thanks i guess.

[Me.B]

I think you have conflicts between them.

As this is not a common error on current sentora setup.

M B