How do I install unbound?

[水上ナツ]

Hello Paul-san

Thank you for your reply.
I was able to start up with the latest version of RHEL.
# rpm -q unbound
unbound-1.6.6-1.el7.x86_64
# systemctl status unbound
-------------------
● unbound.service - Unbound recursive Domain Name Server
   Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; vendor
preset: disabled)
   Active: active (running) since Mon 2019-02-04 11:11:46 JST; 1min 17s ago
 Main PID: 7582 (unbound)
   CGroup: /system.slice/unbound.service
           mq7582 /usr/sbin/unbound -d
 2月 04 11:11:46 example.com systemd[1]: Starting Unbound recursive Domain
Name Server...
 2月 04 11:11:46 example.com unbound-checkconf[7579]: unbound-checkconf: no
errors in /etc/unbound/unbound.conf
 2月 04 11:11:46 example.com systemd[1]: Started Unbound recursive Domain
Name Server.
 2月 04 11:11:46 example.com unbound[7582]: [7582:0] notice: init module 0:
ipsecmod
 2月 04 11:11:46 example.com unbound[7582]: [7582:0] notice: init module 1:
validator
 2月 04 11:11:46 example.com unbound[7582]: [7582:0] notice: init module 2:
iterator
 2月 04 11:11:46 example.com unbound[7582]: [7582:0] info: start of service
(unbound 1.6.6).
-------------------
Problems like the community version did not occur.
Is it community version specific problem? Is it a Bug?
I have an additional question.
I set according to the following document,
Error (can not bind socket: Address already in use for 0.0.0.0 / fatal
error: could not open ports) is output and unbound can not be started.
Please tell me how to resolve.
Setup
https://www.nlnetlabs.nl/documentation/unbound/howto-setup/
# vim /etc/unbound/unbound.conf
-------------------
server:
     interface: 0.0.0.0
     interface: ::0
     access-control: 192.168.0.0/16 allow
     access-control: ::1 allow
     verbosity: 1
-------------------
# systemctl restart unbound
# systemctl status unbound
-------------------
● unbound.service - Unbound recursive Domain Name Server
   Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; vendor
preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-02-04 13:51:53 JST;
17s ago
  Process: 4002 ExecStart=/usr/sbin/unbound -d $UNBOUND_OPTIONS
(code=exited, status=1/FAILURE)
  Process: 4000 ExecStartPre=/usr/sbin/unbound-anchor -a
/var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem (code=exited,
status=0/SUCCESS)
  Process: 3996 ExecStartPre=/usr/sbin/unbound-checkconf (code=exited,
status=0/SUCCESS)
 Main PID: 4002 (code=exited, status=1/FAILURE)
 2月 04 13:51:53 example.com systemd[1]: Starting Unbound recursive Domain
Name Server...
 2月 04 13:51:53 example.com unbound-checkconf[3996]: unbound-checkconf: no
errors in /etc/unbound/unbound.conf
 2月 04 13:51:53 example.com systemd[1]: Started Unbound recursive Domain
Name Server.
 2月 04 13:51:53 example.com unbound[4002]: Feb 04 13:51:53 unbound[4002:0]
error: can't bind socket: Address already in use for 0.0.0.0
 2月 04 13:51:53 example.com unbound[4002]: Feb 04 13:51:53 unbound[4002:0]
fatal error: could not open ports
 2月 04 13:51:53 example.com systemd[1]: unbound.service: main process
exited, code=exited, status=1/FAILURE
 2月 04 13:51:53 example.com systemd[1]: Unit unbound.service entered failed
state.
 2月 04 13:51:53 example.com systemd[1]: unbound.service failed.
-------------------
# tail -f /var/log/messages
-------------------
Feb  4 13:51:53 example.com systemd: Starting Unbound recursive Domain Name
Server...
Feb  4 13:51:53 example.com unbound-checkconf: unbound-checkconf: no errors
in /etc/unbound/unbound.conf
Feb  4 13:51:53 example.com systemd: Started Unbound recursive Domain Name
Server.
Feb  4 13:51:53 example.com unbound: Feb 04 13:51:53 unbound[4002:0] error:
can't bind socket: Address already in use for 0.0.0.0
Feb  4 13:51:53 example.com unbound: Feb 04 13:51:53 unbound[4002:0] fatal
error: could not open ports
Feb  4 13:51:53 example.com systemd: unbound.service: main process exited,
code=exited, status=1/FAILURE
Feb  4 13:51:53 example.com systemd: Unit unbound.service entered failed
state.
Feb  4 13:51:53 example.com systemd: unbound.service failed.
-------------------

2019年2月1日(金) 23:42 Paul Wouters <paul at nohats.ca>:

> On Fri, 1 Feb 2019, 水上ナツ via Unbound-users wrote:
>
> > I installed unbound-1.9.0rc1 from the source. Starting unbound.conf with
> the default, failed to start.
> > Is there anything that you have to set at a minimum? How can I start it?
> >
> > The following is the operation log.
> > ------------------------------------
> > # wget https://nlnetlabs.nl/downloads/unbound/unbound-1.9.0rc1.tar.gz
> > # tar zxvf unbound-1.9.0rc1.tar.gz
> > # ./configure
> > # make
> > # make install
> > # rpm -q openssl-devel
> > openssl-devel-1.0.2k-16.el7.x86_64
>
> On RHEL systems, you can take the latest RHEL source rpm and change the
> version and compile the new unbound packages. Or look at the fedora
> source rpm which are usually newer than the packages in rhel/centos.
>
> Paul
> (although I have not yet tested 1.9.0rc1)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20190204/551fe614/attachment.htm>