Facebook
Twitter
My friend is having issues getting BIND running on CentOS 7 with Plesk 12 and I am offering a hand. You'll have to forgive my rather limited knowledge of setting up DNS servers - it's not my area of expertise and I haven't had to use Linux regularly for some time, so I'm rather rusty.
I have looked at the similar issues on here, but they did not solve the issue.
We have been using the following guide:
http://www.unixmen.com/setting-dns-server-centos-7/
As such, the named.conf is pretty much as you see there, with the following changes:
I've masked the actual domain name with DOMAIN (without the .com TLD, so that is noted separately where appropriate) and the IP address is masked as AAA.BBB.CCC.DDD accordingly.
The forward.DOMAIN file is as follows:
reverse.DOMAIN is very similar to the above. The IN SOA part is identical, but the rest is as follows:
When it comes to starting named, systemctl enable named works fine. However, it won't start.
The results are as follows:
named-checkconf /etc/named.conf gives back nothing (I believe that's good). However, named-checkzone produces an error (the same on forward and reverse files):
I did notice that this post mentioned chroot (we tried using named-chroot too, with errors) and to copy the code from /var/named/chroot/var/named/chroot/etc/named.conf.default to the empty named.conf.
Well, this file didn't exist, but there was one at /var/named/chroot/etc/named.conf.default - following the above instructions and stopping named, I could then use:
systemctl start named-chroot
This didn't produce any errors! Yay! named-checkconf confirms the same.
I now get this:
However, named-checkzone still gives the same error as before, regardless of which location I use for the zone files. I assume this is because it is related to named, not named-chroot?
The named.conf.default that I copied over was quite different - it had stuff about how Plesk was going to overwrite any information I changed, although there was a section where I could add custom directives. I tried copying the contents of my named.conf in there... and it broke it! named-chroot would no longer start, giving errors.
So... can anyone advise me where to go from here?
Incidentally, I don't have access to the Plesk panel right now - my friend left me the login credentials, they were wrong and I locked myself out! He told me that the Plesk panel sees the server root as 127.0.0.1. He also told me BIND wouldn't start via Plesk. I am logging in as root via SSH. He also tried reinstalling BIND, but it hasn't got us any further.
Any assistance would be greatly appreciated.
I have looked at the similar issues on here, but they did not solve the issue.
We have been using the following guide:
http://www.unixmen.com/setting-dns-server-centos-7/
As such, the named.conf is pretty much as you see there, with the following changes:
Code:
allow-query { localhost; AAA.BBB.CCC.DDD;}; ### IP Range ###
allow-transfer { localhost; AAA.BBB.CCC.DDD;}; ### Slave DNS IP ###
zone "DOMAIN.com" IN {
type master;
file "forward.DOMAIN";
allow-update { none; };
};
zone "CCC.BBB.AAA.in-addr.arpa" IN {
type master;
file "reverse.DOMAIN";
allow-update { none; };
};I've masked the actual domain name with DOMAIN (without the .com TLD, so that is noted separately where appropriate) and the IP address is masked as AAA.BBB.CCC.DDD accordingly.
The forward.DOMAIN file is as follows:
Code:
$TTL 86400
@ IN SOA ns1.DOMAIN.com. adminemailaddress.hotmail.com. (
2011071001 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
IN NS ns1.DOMAIN.com.
IN NS ns2.DOMAIN.com.
IN A AAA.BBB.CCC.DDD
IN MX 0 DOMAIN.com.
ns1 IN A AAA.BBB.CCC.DDD
ns2 IN A AAA.BBB.CCC.DDD
mail IN CNAME DOMAIN.com.
www IN CNAME DOMAIN.com.reverse.DOMAIN is very similar to the above. The IN SOA part is identical, but the rest is as follows:
Code:
IN NS ns1.DOMAIN.com.
IN NS ns2.DOMAIN.com.
IN PTR DOMAIN.com.
ns1 IN A AAA.BBB.CCC.DDD
ns2 IN A AAA.BBB.CCC.DDD
IN PTR ns1.DOMAIN.com.
IN PTR ns2.DOMAIN.com.
IN PTR DOMAIN.com.When it comes to starting named, systemctl enable named works fine. However, it won't start.
The results are as follows:
and
named-checkconf /etc/named.conf gives back nothing (I believe that's good). However, named-checkzone produces an error (the same on forward and reverse files):
I did notice that this post mentioned chroot (we tried using named-chroot too, with errors) and to copy the code from /var/named/chroot/var/named/chroot/etc/named.conf.default to the empty named.conf.
Well, this file didn't exist, but there was one at /var/named/chroot/etc/named.conf.default - following the above instructions and stopping named, I could then use:
systemctl start named-chroot
This didn't produce any errors! Yay! named-checkconf confirms the same.
I now get this:
However, named-checkzone still gives the same error as before, regardless of which location I use for the zone files. I assume this is because it is related to named, not named-chroot?
The named.conf.default that I copied over was quite different - it had stuff about how Plesk was going to overwrite any information I changed, although there was a section where I could add custom directives. I tried copying the contents of my named.conf in there... and it broke it! named-chroot would no longer start, giving errors.
So... can anyone advise me where to go from here?
Incidentally, I don't have access to the Plesk panel right now - my friend left me the login credentials, they were wrong and I locked myself out! He told me that the Plesk panel sees the server root as 127.0.0.1. He also told me BIND wouldn't start via Plesk. I am logging in as root via SSH. He also tried reinstalling BIND, but it hasn't got us any further.
Any assistance would be greatly appreciated.
