Re: BIND9 won't start
On Sun, Dec 23, 2007 at 11:45:58PM +0100, QADMOS wrote: Gelsema, P (Patrick) a écrit : On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) Well Patrick i followed your suggestion and rebooted (it didn't do much after just editing rc.conf) the box and now /etc/rc.d/named start works fine annd named is running, 'rndc' still has the same problem though (???) I'm a bit befuddled though, because i don't understand why it's necessary to use the named_enable directive to have named running ? I understand this is necessary if you want the daemon to run at boot time but why is this necessary if you want to run it manually once the box is on ? Well, if you use the rc script or any of the other scripts that might be supplied with it to start it, then that script checks that variable - namely 'named_enable' and if it is not set, the script exits without doing anything. jerry In any case thx a lot for your help :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
BIND9 won't start
Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either there's just no error message despite that the named is not running (checked with ps waux | grep named ) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
Gelsema, P (Patrick) a écrit : On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) Well Patrick i followed your suggestion and rebooted (it didn't do much after just editing rc.conf) the box and now /etc/rc.d/named start works fine annd named is running, 'rndc' still has the same problem though (???) I'm a bit befuddled though, because i don't understand why it's necessary to use the named_enable directive to have named running ? I understand this is necessary if you want the daemon to run at boot time but why is this necessary if you want to run it manually once the box is on ? In any case thx a lot for your help :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
My apologies for the blank post. Apparently, I became a bit trigger happy while setting up Kmail for mailing lists. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Sunday 23 December 2007 05:45:58 pm QADMOS wrote: -- Glen Barber (570)328-0318 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
QADMOS wrote: Gelsema, P (Patrick) a écrit : On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) Well Patrick i followed your suggestion and rebooted (it didn't do much after just editing rc.conf) the box and now /etc/rc.d/named start works fine annd named is running, 'rndc' still has the same problem though (???) I'm a bit befuddled though, because i don't understand why it's necessary to use the named_enable directive to have named running ? I understand this is necessary if you want the daemon to run at boot time but why is this necessary if you want to run it manually once the box is on ? In any case thx a lot for your help :) the entries in the rc.conf are there for system security. [something] might be installed, but its not supposed to be allowed to run unless the system admin knows about it. otherwise, there is always 'forcestart' intead of 'start'. cheers, -- Jonathan Horne http://www.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Dec 23, 2007 3:45 PM, QADMOS [EMAIL PROTECTED] wrote: Gelsema, P (Patrick) a écrit : On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused do you get same problem with: /etc/rc.d/named start Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) Well Patrick i followed your suggestion and rebooted (it didn't do much after just editing rc.conf) the box and now /etc/rc.d/named start works fine annd named is running, 'rndc' still has the same problem though (???) I'm a bit befuddled though, because i don't understand why it's necessary to use the named_enable directive to have named running ? I understand this is necessary if you want the daemon to run at boot time but why is this necessary if you want to run it manually once the box is on ? /etc/rc.d/named is the rc script to control (start, stop etc.) named, and this script is inactive unless you've specified that named is to be enabled using the named_enable variable. You can get around the need to activate the variable by prefixing your commands with the 'force' keyword (e.g. /etc/rc.d/named forcestart, etc.) Use sockstat(1) to figure out if the control port (953/tcp) is listening. 'sockstat -4l' should show a listener on 127.0.0.1:953. Also, 'start' is not a valid command to rndc. You would have a chicken and egg problem; if named has not been started, then there is no service to handle the start command to rndc. Use the rc script to start named and rndc to control its runtime operation. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Monday 24 December 2007 02:15, Jonathan Horne wrote: otherwise, there is always 'forcestart' intead of 'start'. and Darren Spruell wrote: You can get around the need to activate the variable by prefixing your commands with the 'force' keyword (e.g. /etc/rc.d/named forcestart, etc.) To start a service which isn't enabled in rc.conf, it's better to use onestart From the rc.subr(8) manpage: force Skip the checks for rcvar being set to ``YES'', and sets rc_force=YES. This ignores argument_precmd returning non-zero, and ignores any of the required_* tests failing, and always returns a zero exit status. oneSkip the checks for rcvar being set to ``YES'', but performs all the other prerequisite tests. Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Dec 23, 2007 10:43 PM, Jonathan McKeown [EMAIL PROTECTED] wrote: On Monday 24 December 2007 02:15, Jonathan Horne wrote: otherwise, there is always 'forcestart' intead of 'start'. and Darren Spruell wrote: You can get around the need to activate the variable by prefixing your commands with the 'force' keyword (e.g. /etc/rc.d/named forcestart, etc.) To start a service which isn't enabled in rc.conf, it's better to use onestart From the rc.subr(8) manpage: force Skip the checks for rcvar being set to ``YES'', and sets rc_force=YES. This ignores argument_precmd returning non-zero, and ignores any of the required_* tests failing, and always returns a zero exit status. oneSkip the checks for rcvar being set to ``YES'', but performs all the other prerequisite tests. Good to know, thx. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
