Compiling BIND9 on CentOS 7
linuxmailinglistsemail at gmail.com
Mon Apr 25 17:54:31 UTC 2016
Thank you for your response. Let me see if what you provided will work
with what I am trying to do.
On Mon, Apr 25, 2016 at 1:36 PM, Reindl Harald <h.reindl at thelounge.net>
> Am 25.04.2016 um 19:23 schrieb Sean Son:
>> Thank you for your reply.
>> The issue is, I do not know what other services/targets will need to be
>> started prior to BIND starting. In other words, I have no idea how to
>> set up the unit file for BIND.
> none - just none
> and even if - how would a blind script at startup solve that question - if
> it don't (and it really don't) what's your exactly problem?
> Description=DNS Server
> ExecStart=/usr/sbin/named -f -u named
> ExecReload=/usr/bin/kill -HUP $MAINPID
> ExecStop=/usr/bin/kill -TERM $MAINPID
> On Mon, Apr 25, 2016 at 12:09 PM, Anand Buddhdev <anandb at ripe.net
>> <mailto:anandb at ripe.net>> wrote:
>> On 25/04/16 17:59, Sean Son wrote:
>> Hi Sean Son,
>> > I know I emailed the list about compiling BIND on a SystemD distro
>> > last month. This time I have a different question. After I compile
>> BIND9 on
>> > CentOS 7 , how do I get it to start up at boot time and how do I
>> > it? I don't want to have to write a systemd unit configuration file
>> for it.
>> > I want it to run using a boot script or some other way that will
>> allow BIND
>> > to start up at boot and also allow the system administrator to
>> restart BIND
>> > if it ever stops running.
>> A systemd unit file is the *easiest* and *simplest* way to get BIND to
>> start at boot. Is there any reason you don't want to use systemd? It's
>> not difficult at all. You just a few lines in a file to create a
>> If you don't want systemd to restart BIND if it crashes, then you can
>> just set:
>> Then, you can start BIND by hand with "systemctl start <unitname>"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users