Main web site working fine, but others not. - VictoryAndGlory - 03-21-2018
Hi eveyone, I was using vestacp but that was too buggy and i found sentora.
Now, I installed sentora to my VDS. My main website is "www.glorywebscript.com" and sentora panel "glorywebscript.com"
I added the domain named "hzmeth.tk" (I pointed the nameservers ns1.glory- ns2 etc.)
After a few minutes it became live. Then I created DNS records for "hzmeth.tk" in the sentora panel.
Its been two days yet it cannot find the website. But i can browse "www.glorywebscript.com"
![[Image: XPgnR7.png]](https://i.hizliresim.com/XPgnR7.png)
And these were created automatically:
![[Image: bB0O78.png]](https://i.hizliresim.com/bB0O78.png)
Shouldn't they be like ns1.glorywebscript.com ? why ns1.hzmeth?
Also hzmeth.tk and gloryws.tk throws this: Loop detected! We were referred back to '***.***.***.213'
RE: Main web site working fine, but others not. - Me.B - 03-21-2018
Did you point domain to use sentora dns with your domain registerar?
https://intodns.com/hzmeth.tk
Seem you didn't create the DNS records.
M B
RE: Main web site working fine, but others not. - VictoryAndGlory - 03-21-2018
(03-21-2018, 06:07 PM)Me.B Wrote: Did you point domain to use sentora dns with your domain registerar?
https://intodns.com/hzmeth.tk
Seem you didn't create the DNS records.
M B I did.
1:
http://prntscr.com/iu657w
2:
http://prntscr.com/iu65rw
3:
http://prntscr.com/iu669h
And this is the the domain I setup sentora(godaddy):
http://prntscr.com/iu67i2 (www.glorywebscript.com)
RE: Main web site working fine, but others not. - Me.B - 03-21-2018
Is sentora cron running? To update DNS?
M B
RE: Main web site working fine, but others not. - VictoryAndGlory - 03-21-2018
(03-21-2018, 06:28 PM)Me.B Wrote: Is sentora cron running? To update DNS?
M B
I think it is running:
http://prntscr.com/iu6uvj
Datetime is correct in my timezone.
RE: Main web site working fine, but others not. - Me.B - 03-21-2018
Could you check bind logs and see if the zone is created?
M B
RE: Main web site working fine, but others not. - VictoryAndGlory - 03-21-2018
(03-21-2018, 07:18 PM)Me.B Wrote: Could you check bind logs and see if the zone is created?
M B
Oh :O
BIND Errors:
Quote:19-Mar-2018 20:47:47.972 general: error: managed-keys.bind.jnl: create: permission denied
19-Mar-2018 20:47:47.972 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
19-Mar-2018 20:47:47.972 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
19-Mar-2018 20:48:06.142 general: error: managed-keys.bind.jnl: create: permission denied
19-Mar-2018 20:48:06.142 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
19-Mar-2018 20:48:06.142 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
19-Mar-2018 20:48:51.225 general: error: managed-keys.bind.jnl: create: permission denied
19-Mar-2018 20:48:51.227 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
19-Mar-2018 20:48:51.227 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
19-Mar-2018 21:15:01.495 general: error: managed-keys.bind.jnl: create: permission denied
19-Mar-2018 21:15:01.495 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
19-Mar-2018 21:15:01.495 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
19-Mar-2018 23:10:02.164 general: error: managed-keys.bind.jnl: create: permission denied
19-Mar-2018 23:10:02.164 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
19-Mar-2018 23:10:02.164 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
20-Mar-2018 01:04:54.382 general: error: managed-keys.bind.jnl: create: permission denied
20-Mar-2018 01:04:54.383 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
20-Mar-2018 01:04:54.383 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
21-Mar-2018 04:34:46.380 security: error: client 64.20.227.131#65118 (glorywebscript.com): zone transfer 'glorywebscript.com/AXFR/IN' denied
21-Mar-2018 04:34:46.381 security: error: client 64.20.227.131#65119 (glorywebscript.com): zone transfer 'glorywebscript.com/AXFR/IN' denied
21-Mar-2018 09:52:30.134 security: error: client 176.221.80.21#57926 (ceshar.tk): zone transfer 'ceshar.tk/AXFR/IN' denied
21-Mar-2018 09:52:31.661 security: error: client 176.221.80.21#57930 (ceshar.tk): zone transfer 'ceshar.tk/AXFR/IN' denied
21-Mar-2018 09:58:06.921 security: error: client 176.221.80.21#58857 (glorywebscript.com): zone transfer 'glorywebscript.com/AXFR/IN' denied
21-Mar-2018 09:58:08.544 security: error: client 176.221.80.21#58865 (glorywebscript.com): zone transfer 'glorywebscript.com/AXFR/IN' denied
21-Mar-2018 10:05:31.011 security: error: client 192.134.4.86#58184 (ceshar.tk): zone transfer 'ceshar.tk/AXFR/IN' denied
21-Mar-2018 10:05:31.156 security: error: client 192.134.4.86#58186 (ceshar.tk): zone transfer 'ceshar.tk/AXFR/IN' denied
21-Mar-2018 10:05:31.299 security: error: client 192.134.4.86#58188 (ceshar.tk): zone transfer 'ceshar.tk/AXFR/IN' denied
21-Mar-2018 10:05:31.441 security: error: client 192.134.4.86#58190 (ceshar.tk): zone transfer 'ceshar.tk/AXFR/IN' denied
21-Mar-2018 10:44:06.522 general: error: managed-keys.bind.jnl: create: permission denied
21-Mar-2018 10:44:06.523 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
21-Mar-2018 10:44:06.523 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
21-Mar-2018 11:04:25.591 general: error: managed-keys.bind.jnl: create: permission denied
21-Mar-2018 11:04:25.593 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
21-Mar-2018 11:04:25.593 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
21-Mar-2018 11:30:47.344 general: error: managed-keys.bind.jnl: create: permission denied
21-Mar-2018 11:30:47.345 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
21-Mar-2018 11:30:47.345 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
21-Mar-2018 12:22:51.561 general: error: managed-keys.bind.jnl: create: permission denied
21-Mar-2018 12:22:51.565 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
21-Mar-2018 12:22:51.565 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
BIND Warnings:
Quote:19-Mar-2018 21:15:01.492 security: warning: using built-in DLV key for view _default
19-Mar-2018 23:10:02.159 security: warning: using built-in DLV key for view _default
RE: Main web site working fine, but others not. - VictoryAndGlory - 03-21-2018
etc/named/ folder is empty. Something is wrong
Sorry for bumping again, I found a named.conf in etc/named.conf and i found another named.conf in etc/sentora/configs/bind/ and i found another named.conf in etc/sentora/configs/bind/etc/named.conf
I am super confused right now.
Also there is two files in zones which they are the only domains working fine in server. (ceshar.tk and glorywebscript.com)
Would it work if I manually create these files for other domains? Or should I?
RE: Main web site working fine, but others not. - Me.B - 03-21-2018
Don't use PM. I will help here.
Did you try to add dnsec ?
There is a symbolic link setup so bind use the config in sentora/configs folder instead.
Did you change any of these?
RE: Main web site working fine, but others not. - VictoryAndGlory - 03-22-2018
(03-21-2018, 11:00 PM)Me.B Wrote: Don't use PM. I will help here.
Did you try to add dnsec ?
There is a symbolic link setup so bind use the config in sentora/configs folder instead.
Did you change any of these?
No, I never used linux before. So I didnt want to change any of it before asking it's experts.
But I think its in these files already:
named.conf 1:
Quote:options {
listen-on port 53 { any; };
listen-on-v6 port 53 { any; };
allow-query { any; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
recursion no;
dnssec-enable yes;
dnssec-validation yes;
dnssec-lookaside auto;
/* Path to ISC DLV key */
bindkeys-file "/etc/named.iscdlv.key";
};
named.conf 2:
Quote:options {
listen-on port 53 { any; };
listen-on-v6 port 53 { any; };
allow-query { any; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
recursion no;
dnssec-enable yes;
dnssec-validation yes;
dnssec-lookaside auto;
/* Path to ISC DLV key */
bindkeys-file "/etc/named.iscdlv.key";
};
Quote:21-Mar-2018 19:00:10.359 general: error: managed-keys.bind.jnl: create: permission denied
21-Mar-2018 19:00:10.359 general: error: managed-keys-zone: sync_keyzone:dns_journal_open -> unexpected error
21-Mar-2018 19:00:10.359 general: error: managed-keys-zone: unable to synchronize managed keys: unexpected error
21-Mar-2018 19:00:10.364 general: notice: all zones loaded
21-Mar-2018 19:00:10.364 general: notice: running
Edit: alright, i tried to change these 3 lines in named.conf in every way. enable no, validation no, enable yes, validation auto, but it gives same error again and again.
|