Non-responsive name servers when started during boot on OS X Mavericks 10.9
Larry Stone
lstone19 at stonejongleux.com
Wed Jan 22 19:11:53 UTC 2014
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 Network, or you'd have to
> duplicate Apple's solution (probably by sending need a SIGHUP when the
> network is live).
This discussion is going full circle (although part of it may have been a
couple of private emails I was sent). I speculated that Apple was making
undocumented patches to bind and someone said no, it's as distributed.
But this is why I really like installing from source - too many packagers
making undocumented changes that cause software to behave differently than
the documentation says it till.
But I will get to testing your ideas. In the meantime, with a startup
delay script and an hourly monitoring job, I have a "comfortable"
environment.
-- Larry Stone
lstone19 at stonejongleux.com
More information about the bind-users
mailing list