Bind 9.3.0 on FreeBSD 5.3.
I need some help setting up Bind 9.3.0 on FreeBSD 5.3. Here is my setup: edit /etc/rc.conf named_enable=YES named_chrotdir=/var/named named_chroot_autoupdate=YES Generate rndc.key, create rndc.conf, place rndc.key in named.conf and rndc.conf Create Forward zone, reverse zone, loopback Place my named server in /etc/resolv.conf Rebooted, then I tried the following: hazika# dig ; DiG 9.3.0 ;; global options: printcmd ;; connection timed out; no servers could be reached hazika# /etc/rc.d/named stop named not running? (check /var/run/named/pid). hazika# /etc/rc.d/named start hazika# ps -aux | grep 'named' root 670 0.0 0.8 1620 972 p1 R+ 12:21PM 0:00.02 grep named hazika# netstat -an | grep '.53 Unmatched '. hazika# rndc start rndc: connect failed: connection refused Some help please, it seems Bind is not running. -- Rodrique Heron Independent Network Consultant (MS Window's Flavors, FreeBSD, Fedora) --- pH:718-255-5876 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 9.3.0 on FreeBSD 5.3
On 2004-12-31 10:35, Gerard Samuel [EMAIL PROTECTED] wrote: J.D. Bronson wrote: At 09:07 AM 12/31/2004, Richard Cotrina wrote: Is there any reason for not using bind 9.3.0 that comes with FreeBSD 5.3 ? It can be run chrooted with the same flags you are using. I deleted it by accident. I dont know how to re-make the OEM version that comes with 5.3I posted it and no one replied. Google has not been much help... I may be wrong, but wouldn't a fresh pull from cvsup, and a build/installworld, restore bind and friends??? Yes. That would be the best thing to do, IMHO. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
9.3.0 on FreeBSD 5.3
It compiles fine and runs fine...but I noticed an odd thing. When the MASTER DNS server boots up, it fails to send notifies to the SLAVES: 31-Dec-2004 06:51:33.207 zone domain.com/IN/external: notify to 1.1.1.1#53: retries exceeded (tons of them..each referring to each of my domains or zones) None of the slaves ever see the NOTIFY. ..here is the odd part: If I kill off named (after boot is all done)...then launch it again, the SLAVES now receive the NOTIFYs. So its *only* during the boot-up sequence that I am seeing this. Bind 9.3.0 starts in the SAME way as the OEM version that comes with FREEBSD 5.3 with 2 exceptions. 1. I run it chrooted to /var/named 2. In rc.conf, I simply specify my new compiled binary and launch it as such: named_enable=YES named_program=/usr/local/sbin/named named_flags=-t /var/named -u named Anyone have ANY insight on this? -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282 This message should contain confidential and/or privileged information, but it doesn't. If you are not the addressee or authorized to receive this for the addressee, go ahead, copy, disclose, or take any action based on this message or any information herein that you wish, what the heck! If you have received this message in error, please ask the sender what the heck they were thinking about. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 9.3.0 on FreeBSD 5.3
Is there any reason for not using bind 9.3.0 that comes with FreeBSD 5.3 ? It can be run chrooted with the same flags you are using. Regarding your question, I suposse your master server can't connect to your slaver server on port tcp 53 which is used for transfer zones and master-slave notifications because of some packet filter. Do you have any tcp-wrapper, ipfw or ipf rules that may be blocking the establishment of tcp session on port 53 ? - Original Message - From: J.D. Bronson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Friday, December 31, 2004 8:04 AM Subject: 9.3.0 on FreeBSD 5.3 It compiles fine and runs fine...but I noticed an odd thing. When the MASTER DNS server boots up, it fails to send notifies to the SLAVES: 31-Dec-2004 06:51:33.207 zone domain.com/IN/external: notify to 1.1.1.1#53: retries exceeded (tons of them..each referring to each of my domains or zones) None of the slaves ever see the NOTIFY. ..here is the odd part: If I kill off named (after boot is all done)...then launch it again, the SLAVES now receive the NOTIFYs. So its *only* during the boot-up sequence that I am seeing this. Bind 9.3.0 starts in the SAME way as the OEM version that comes with FREEBSD 5.3 with 2 exceptions. 1. I run it chrooted to /var/named 2. In rc.conf, I simply specify my new compiled binary and launch it as such: named_enable=YES named_program=/usr/local/sbin/named named_flags=-t /var/named -u named Anyone have ANY insight on this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 9.3.0 on FreeBSD 5.3
Is there any reason for not using bind 9.3.0 that comes with FreeBSD 5.3 ? It can be run chrooted with the same flags you are using. Regarding your question, I suposse your master server can't connect to your slaver server on port tcp 53 which is used for transfer zones and master-slave notifications because of some packet filter. Do you have any tcp-wrapper, ipfw or ipf rules that may be blocking the establishment of tcp session on port 53 ? - Original Message - From: J.D. Bronson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Friday, December 31, 2004 8:04 AM Subject: 9.3.0 on FreeBSD 5.3 It compiles fine and runs fine...but I noticed an odd thing. When the MASTER DNS server boots up, it fails to send notifies to the SLAVES: 31-Dec-2004 06:51:33.207 zone domain.com/IN/external: notify to 1.1.1.1#53: retries exceeded (tons of them..each referring to each of my domains or zones) None of the slaves ever see the NOTIFY. ..here is the odd part: If I kill off named (after boot is all done)...then launch it again, the SLAVES now receive the NOTIFYs. So its *only* during the boot-up sequence that I am seeing this. Bind 9.3.0 starts in the SAME way as the OEM version that comes with FREEBSD 5.3 with 2 exceptions. 1. I run it chrooted to /var/named 2. In rc.conf, I simply specify my new compiled binary and launch it as such: named_enable=YES named_program=/usr/local/sbin/named named_flags=-t /var/named -u named Anyone have ANY insight on this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 9.3.0 on FreeBSD 5.3
Is there any reason for not using bind 9.3.0 that comes with FreeBSD 5.3 ? It can be run chrooted with the same flags you are using. Regarding your question, I suposse your master server can't connect to your slaver server on port tcp 53 which is used for transfer zones and master-slave notifications because of some packet filter. Do you have any tcp-wrapper, ipfw or ipf rules that may be blocking the establishment of tcp session on port 53 ? - Original Message - From: J.D. Bronson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Friday, December 31, 2004 8:04 AM Subject: 9.3.0 on FreeBSD 5.3 It compiles fine and runs fine...but I noticed an odd thing. When the MASTER DNS server boots up, it fails to send notifies to the SLAVES: 31-Dec-2004 06:51:33.207 zone domain.com/IN/external: notify to 1.1.1.1#53: retries exceeded (tons of them..each referring to each of my domains or zones) None of the slaves ever see the NOTIFY. ..here is the odd part: If I kill off named (after boot is all done)...then launch it again, the SLAVES now receive the NOTIFYs. So its *only* during the boot-up sequence that I am seeing this. Bind 9.3.0 starts in the SAME way as the OEM version that comes with FREEBSD 5.3 with 2 exceptions. 1. I run it chrooted to /var/named 2. In rc.conf, I simply specify my new compiled binary and launch it as such: named_enable=YES named_program=/usr/local/sbin/named named_flags=-t /var/named -u named Anyone have ANY insight on this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 9.3.0 on FreeBSD 5.3
Is there any reason for not using bind 9.3.0 that comes with FreeBSD 5.3 ? It can be run chrooted with the same flags you are using. Regarding your question, I suposse your master server can't connect to your slaver server on port tcp 53 which is used for transfer zones and master-slave notifications because of some packet filter. Do you have any tcp-wrapper, ipfw or ipf rules that may be blocking the establishment of tcp session on port 53 ? - Original Message - From: J.D. Bronson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Friday, December 31, 2004 8:04 AM Subject: 9.3.0 on FreeBSD 5.3 It compiles fine and runs fine...but I noticed an odd thing. When the MASTER DNS server boots up, it fails to send notifies to the SLAVES: 31-Dec-2004 06:51:33.207 zone domain.com/IN/external: notify to 1.1.1.1#53: retries exceeded (tons of them..each referring to each of my domains or zones) None of the slaves ever see the NOTIFY. ..here is the odd part: If I kill off named (after boot is all done)...then launch it again, the SLAVES now receive the NOTIFYs. So its *only* during the boot-up sequence that I am seeing this. Bind 9.3.0 starts in the SAME way as the OEM version that comes with FREEBSD 5.3 with 2 exceptions. 1. I run it chrooted to /var/named 2. In rc.conf, I simply specify my new compiled binary and launch it as such: named_enable=YES named_program=/usr/local/sbin/named named_flags=-t /var/named -u named Anyone have ANY insight on this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 9.3.0 on FreeBSD 5.3
At 09:07 AM 12/31/2004, Richard Cotrina wrote: Is there any reason for not using bind 9.3.0 that comes with FreeBSD 5.3 ? It can be run chrooted with the same flags you are using. I deleted it by accident. I dont know how to re-make the OEM version that comes with 5.3I posted it and no one replied. Google has not been much help... Regarding your question, I suposse your master server can't connect to your slaver server on port tcp 53 which is used for transfer zones and master-slave notifications because of some packet filter. Do you have any tcp-wrapper, ipfw or ipf rules that may be blocking the establishment of tcp session on port 53 ? There is no pf or ipf or anything on this box. Humm. - Original Message - From: J.D. Bronson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Friday, December 31, 2004 8:04 AM Subject: 9.3.0 on FreeBSD 5.3 It compiles fine and runs fine...but I noticed an odd thing. When the MASTER DNS server boots up, it fails to send notifies to the SLAVES: 31-Dec-2004 06:51:33.207 zone domain.com/IN/external: notify to 1.1.1.1#53: retries exceeded (tons of them..each referring to each of my domains or zones) None of the slaves ever see the NOTIFY. ..here is the odd part: If I kill off named (after boot is all done)...then launch it again, the SLAVES now receive the NOTIFYs. So its *only* during the boot-up sequence that I am seeing this. Bind 9.3.0 starts in the SAME way as the OEM version that comes with FREEBSD 5.3 with 2 exceptions. 1. I run it chrooted to /var/named 2. In rc.conf, I simply specify my new compiled binary and launch it as such: named_enable=YES named_program=/usr/local/sbin/named named_flags=-t /var/named -u named Anyone have ANY insight on this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282 This message should contain confidential and/or privileged information, but it doesn't. If you are not the addressee or authorized to receive this for the addressee, go ahead, copy, disclose, or take any action based on this message or any information herein that you wish, what the heck! If you have received this message in error, please ask the sender what the heck they were thinking about. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 9.3.0 on FreeBSD 5.3
J.D. Bronson wrote: At 09:07 AM 12/31/2004, Richard Cotrina wrote: Is there any reason for not using bind 9.3.0 that comes with FreeBSD 5.3 ? It can be run chrooted with the same flags you are using. I deleted it by accident. I dont know how to re-make the OEM version that comes with 5.3I posted it and no one replied. Google has not been much help... I may be wrong, but wouldn't a fresh pull from cvsup, and a build/installworld, restore bind and friends??? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
