View Full Version : How rndc is configured to use it in ISPconfig?
tom
27th November 2006, 20:30
1.
If I try to use rndc to tell bind something I get this:
server01:~# rndc status
rndc: connect failed: connection refused
Maybe rndc is configured specialy for ISPconfig?
2.
A secound thing I'm woudering about is that always two bind proceses are running. I don't understand why. Is that maybe even an typical ISPconfig setting?
till
28th November 2006, 11:03
1) ISPConfig does not configure RNDC at all. ISPConfig writes only the named.conf and the pri.... files for the domains.
2) There is no special setting for ISPConfig. When you stop bind with the script in /etc/init.d, is there still a named process left?
tom
28th November 2006, 21:02
1) ISPConfig does not configure RNDC at all. ISPConfig writes only the named.conf and the pri.... files for the domains.
2) There is no special setting for ISPConfig. When you stop bind with the script in /etc/init.d, is there still a named process left?
It's not possible to stop bind9 with the init script. I did the following and you see what the anwser was. I don't understand why I cant use rndc. I've configured rndc now but now and even before I can't use rndc.
1.
Why?
2.
The init script starts only one bind proces but after reboot there are two.
after reboot:
server01:~# /etc/init.d/bind9 stop
Stopping domain name service: namedrndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
.
server01:~# ps aux|grep bind
bind 1053 0.0 1.6 29396 2584 ? Ss 19:51 0:00 /usr/sbin/named -u bind -t /var/lib/named
bind 1746 0.2 1.8 29592 2896 ? Ss 19:52 0:00 /usr/sbin/named -u bind -t /var/lib/named
root 1903 0.0 0.3 1632 520 pts/0 S+ 19:53 0:00 grep bind
server01:~# kill 1053
server01:~# kill 1746
server01:~# ps aux|grep bind
root 1907 0.0 0.3 1632 480 pts/0 R+ 19:54 0:00 grep bind
server01:~# /etc/init.d/bind9 start
Starting domain name service: named.
server01:~# ps aux|grep bind
bind 1916 0.3 1.6 29396 2576 ? Ss 19:54 0:00 /usr/sbin/named -u bind -t /var/lib/named
root 1923 0.0 0.3 1632 480 pts/0 R+ 19:54 0:00 grep bind
server01:~# rndc status
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
falko
29th November 2006, 16:44
Please check the named startup symlinks in /etc/rc3.d, /etc/rc5.d, etc. Maybe you have more than one startup symlink?
tom
29th November 2006, 18:39
Please check the named startup symlinks in /etc/rc3.d, /etc/rc5.d, etc. Maybe you have more than one startup symlink?
1.
Do I need to have this startup symlinks?
server01:/etc# find /etc/ -name "*bind*"
/etc/default/bind9
/etc/init.d/bind9
/etc/rc0.d/K85bind9
/etc/rc1.d/K85bind9
/etc/rc2.d/S15bind9
/etc/rc3.d/S15bind9
/etc/rc4.d/S15bind9
/etc/rc5.d/S15bind9
/etc/rc6.d/K85bind9
/etc/bind
/etc/bind/bind
2.
Could the reason of the impossibility of the usage of rndc be that bind is running chrooted? And if yes what should I do to to get the usage of rndc?
server01:~# rndc status
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
falko
30th November 2006, 16:55
1.
Do I need to have this startup symlinks?Yes.
2.
Could the reason of the impossibility of the usage of rndc be that bind is running chrooted? And if yes what should I do to to get the usage of rndc?
It could also be a permissions problem, as described in the comments on http://www.howtoforge.com/howto_bind_chroot_debian
tom
1st December 2006, 00:12
Yes.
It could also be a permissions problem, as described in the comments on http://www.howtoforge.com/howto_bind_chroot_debian
I've renewed bind according to the bind chroot howto but still I've two bind proceses after reboot and I'm not able to use rndc.
tom
4th December 2006, 14:01
No ideas?
:)
falko
5th December 2006, 19:03
No ideas from my side.
tom
7th December 2006, 01:36
I've just tried to start and restart bind9 with
/etc/init.d/bind9 start|restart but during that a new process of bind is created an no old one are killed. Is'nt it strage?
vBulletin® v3.8.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.