In message , Tony
Finch writes:
> Reindl Harald wrote:
> >
> > > The problem that I alluded to above is that if you have services that
> > > depend on the DNS, there should be a mechanism for the DNS server to say
> > > when it is ready and that it's OK to start services that need DNS. I don't
>
On 22/03/2016 16:44, Bob Harold wrote:
> I appreciate the announcement of the change ahead of time, but I don't feel
> like it is safe to update my root hints file based on an email, which could
> be spoofed. It's not that I don't trust you, but someone could spoof your
> email.
> So I am waiti
Hi,
I have a fedora23 system with bind-9.10.3 that's been running fine for
a long time. For some reason this morning, queries started timing out.
This is a mail server, so queries to spamhaus, barracuda, etc, started
timing out with:
Mar 23 14:46:57 mail03 postfix/postscreen[12635]: warning: dnsb
Anand Buddhdev wrote:
> Knot DNS, for example, has a compile-time option to link against systemd
> libraries. Then, when Knot starts, it loads all its zones in, does
> whatever else it needs to do, and then sends a notification via dbus.
>
> If anyone cares about this, they could open a feature re
On 23/03/16 14:51, Tony Finch wrote:
>> With systemd the methodology isn't that BIND notifies other things that
>> it is up. It is that other things, if dependent upon BIND, have in
>> their systemd files a requirement that BIND be up before they start.
>
> Yes, but how does systemd know when BI
On Wed, Mar 23, 2016 at 01:51:58PM +, Tony Finch wrote:
> Lightner, Jeff wrote:
> >
> > With systemd the methodology isn't that BIND notifies other things that
> > it is up. It is that other things, if dependent upon BIND, have in
> > their systemd files a requirement that BIND be up before t
It doesn't. The systemd script either succeeds or fails. Any script that is
dependent on it succeeding won't start.
Again it is a change.
In init you'd see a start had failed (or was hung).
In systemd it simply sends the instruction to start everything that is supposed
to start. T
Lightner, Jeff wrote:
>
> With systemd the methodology isn't that BIND notifies other things that
> it is up. It is that other things, if dependent upon BIND, have in
> their systemd files a requirement that BIND be up before they start.
Yes, but how does systemd know when BIND is up?
(The Red
Reindl Harald wrote:
> Am 23.03.2016 um 13:36 schrieb Tony Finch:
> >
> > BIND does not do that - it forks too early. It's a bit tiresome
>
> than this is a bug in BIND which should be fixed instead worked around -
Yes.
> the whol epurpose of double-forking is to signal to the caller that
> init
Since there are BIND packages (9.9.4) for RHEL7/CentOS7 available from default
repositories you could download those packages and extract the systemd files
from them and examine what they've done.
With systemd the methodology isn't that BIND notifies other things that it is
up. It is that othe
Reindl Harald wrote:
>
> > The problem that I alluded to above is that if you have services that
> > depend on the DNS, there should be a mechanism for the DNS server to say
> > when it is ready and that it's OK to start services that need DNS. I don't
> > know the right way to specify that to sys
Reindl Harald wrote:
> Am 23.03.2016 um 11:54 schrieb Tony Finch:
> >
> > There's a sample unit file in the chroot setup instructions at
> > https://wiki.debian.org/Bind9
> >
> > (It looks a bit half-baked to me since it doesn't seem to have any way to
> > signal systemd that named has finished st
Sean Son wrote:
>
> I recently compiled and installed BIND 9.10.3-p4 from source on a system
> running CentOS 7. This is for practice purposes. Ive been searching all of
> the net and I cannot find the answer to this one question of mine: How do I
> create the systemd service unit configuration fi
13 matches
Mail list logo
