Re: Non-responsive name servers when started during boot on OS X Mavericks 10.9

2014-01-18 Thread Eduardo Bonsi
Larry, Your problem is that You are mistaken where to find help for your issue. This list is for issues related to BIND only. I still think that your problem could be fix just by installing bind again. You think is not! Then as far as is concerned, you already received enough information to fix

Re: Non-responsive name servers when started during boot on OS X Mavericks 10.9

2014-01-18 Thread Larry Stone
Eduardo - You’re not really reading what the problem is. When named is started as part of system boot, it is running but non-responsive. When started any time later, it works fine. BIND version is latest and greatest 9.8.6 download from ISC just a few days ago - BIND 9.8.6-P2 (have not looked

Re: Non-responsive name servers when started during boot on OS X Mavericks 10.9

2014-01-18 Thread Eduardo Bonsi
It is possible then that when you copied the BIND files back to 10.9, something got broken along the way? I am suspecting that is your BIND package itself! Forget about your actual BIND package, it is outdated! 1. Go to support.menandmice.com (http://support.menandmice.com/download/bind/macosx/

RE: transfer signed zone

2014-01-18 Thread tlarsen
<<< text/html; charset="utf-8": Unrecognized >>> ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users

Re: Non-responsive name servers when started during boot on OS X Mavericks 10.9

2014-01-18 Thread Larry Stone
That is not the problem. Named does start at boot but it is non-responsive (with further thought, perhaps it is for some reason not listening on port 53). When killed and restarted, it then works fine. I am not familiar with macshadows.com but those directions are incomplete and and assume the

Re: transfer signed zone

2014-01-18 Thread Mark Andrews
A zone transfer starts and ends with a SOA record. This server added a SIG record for the SOA after the final SOA. example.com.            86400 IN        SOA     ns1.example.com. hostmaster.example.com. 2014011701 10800 15 604800 10800 example.com.          Â