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

2014-01-25 Thread Larry Stone
On Jan 21, 2014, at 11:38 PM, LuKreme krem...@kreme.com wrote: In the launchd plist do you have something like I finally got around to testing both of these. dict keyNetworkState/key true/ /dict Had no effect. or maybe keyinetdCompatibility/key dict keyWait/key true/

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

2014-01-25 Thread Larry Stone
On Jan 22, 2014, at 12:27 PM, LuKreme krem...@kreme.com wrote: Right, but Apple did this by having their compile of bind start listening on 127.0.0.1 and then prodding it once the network was up and the IP address was available. Since Apple doesn't take this extra step, you'd need to tell

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

2014-01-25 Thread Larry Stone
On Jan 21, 2014, at 5:32 AM, Carsten Strotmann c...@strotmann.de wrote: Hi Chris, Chris Buxton cli...@buxtonfamily.us writes: I’d bet that the package from Men Mice includes this script or an equivalent workaround. When I wrote the original script I wrote about above, I worked at Men

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

2014-01-22 Thread Larry Stone
On Jan 21, 2014, at 11:38 PM, LuKreme krem...@kreme.com wrote: On 18 Jan 2014, at 06:52 , Larry Stone lston...@stonejongleux.com wrote: That is not the problem. In the launchd plist do you have something like dict keyNetworkState/key true/ /dict or maybe

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

2014-01-22 Thread LuKreme
On 22 Jan 2014, at 05:37 , Larry Stone lston...@stonejongleux.com wrote: On Jan 21, 2014, at 11:38 PM, LuKreme krem...@kreme.com wrote: On 18 Jan 2014, at 06:52 , Larry Stone lston...@stonejongleux.com wrote: That is not the problem. In the launchd plist do you have something like

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

2014-01-22 Thread Larry Stone
On Wed, 22 Jan 2014, LuKreme wrote: Right, but Apple did this by having their compile of bind start listening on 127.0.0.1 and then prodding it once the network was up and the IP address was available. Since Apple doesn't take this extra step, you'd need to tell launchd to wait for the

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

2014-01-21 Thread Carsten Strotmann
Hi Chris, Chris Buxton cli...@buxtonfamily.us writes: I’d bet that the package from Men Mice includes this script or an equivalent workaround. When I wrote the original script I wrote about above, I worked at Men Mice. Your script or the sleep timer is not in the package anymore, but maybe

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

2014-01-21 Thread Larry Stone
On Jan 21, 2014, at 5:32 AM, Carsten Strotmann c...@strotmann.de wrote: Hi Chris, Chris Buxton cli...@buxtonfamily.us writes: I’d bet that the package from Men Mice includes this script or an equivalent workaround. When I wrote the original script I wrote about above, I worked at Men

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

2014-01-21 Thread LuKreme
On 18 Jan 2014, at 06:52 , Larry Stone lston...@stonejongleux.com wrote: That is not the problem. In the launchd plist do you have something like dict keyNetworkState/key true/ /dict or maybe keyinetdCompatibility/key dict keyWait/key true/ /dict to tell the system not to start

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

2014-01-20 Thread Chris Buxton
On Jan 17, 2014, at 6:45 PM, Larry Stone lston...@stonejongleux.com wrote: Background: I have been using my Macintosh as a server… […] Problem: This morning, by happenstance, both were rebooted a few minutes apart and suddenly, nobody could access anything. Finally figured out that named

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

2014-01-20 Thread Larry Stone
On Jan 20, 2014, at 1:22 PM, Chris Buxton cli...@buxtonfamily.us wrote: Problem: This morning, by happenstance, both were rebooted a few minutes apart and suddenly, nobody could access anything. Finally figured out that named on both was not responding (queries timed out). Killed named

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: Non-responsive name servers when started during boot on OS X Mavericks 10.9

2014-01-18 Thread Eduardo Bonsi
AM Subject: Re: Non-responsive name servers when started during boot on OS X Mavericks 10.9 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

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

2014-01-18 Thread Eduardo Bonsi
...@stonejongleux.com To: bind-users@lists.isc.org bind-users@lists.isc.org Sent: Saturday, January 18, 2014 4:15 PM Subject: Re: Non-responsive name servers when started during boot on OS X Mavericks 10.9 Eduardo - You’re not really reading what the problem is. When named is started as part

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

2014-01-17 Thread Eduardo Bonsi
Hello Larry, I had the same head-ache when I upgraded to 10.9. It seems that instead going forward we all took a step behind. I guess this type of free stuff does come with something attached to it. Anyways, when you upgraded to 10.9 the boot files were wipe clean from the