20 Srp
2015
20 Srp
'15
11:32
It works just well right now.
# idig example.com @localhost
example.com. 900 IN A 106.185.25.206
# idig txt chaos version.bind @localhost
version.bind. 0 CH TXT "Knot DNS 2.0.0"
I will look further into the documentation, may use knotd to replace
one/more of our BIND servers. We have about 50,000 zones powered by BIND
before. Thanks a lot.
On 2015/8/20 星期四 17:25, Ondřej Surý wrote:
Perhaps you are running it under upstart or systemd?
Try something like:
service knot stop
Cheers, Ondřej
On August 20, 2015 11:11:26 AM GMT+02:00, Ken Peng <kpeng(a)runbox.com> wrote:
Do you know why knotd can't be stopped?
# ps -efw|grep knot
root 16617 1 0 09:05 ? 00:00:00 /usr/sbin/knotd -c
/etc/knot/knot.conf
root 16643 14461 0 09:07 pts/0 00:00:00 grep --color=auto knot
# killall knotd
# ps -efw|grep knot
root 16649 1 0 09:08 ? 00:00:00 /usr/sbin/knotd -c
/etc/knot/knot.conf
root 16667 14461 0 09:08 pts/0 00:00:00 grep --color=auto knot
# knotc stop
stopping server
# ps -efw|grep knot
root 16673 1 0 09:08 ? 00:00:00 /usr/sbin/knotd -c
/etc/knot/knot.conf
root 16691 14461 0 09:08 pts/0 00:00:00 grep --color=auto knot
As you see, both "killall" and "knotc stop" doesn't make the
daemon
exit, but a new process (with new process ID) appeared.
Thank you.
On 2015/8/20 星期四 16:45, Ondřej Surý wrote:
You can change that in the config file - section system (there's
documentation on the web).
I'll look into the package since it should be automatic.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.