Project

General

Profile

Actions
Copy link

Feature #10389

closed

2.4.5: *reload* unbound to avoid constant service outages, rather than restart

Added by Brittney Lars over 4 years ago. Updated over 4 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
03/29/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Unbound is not fast to restart:

Jan 21 01:56:37 airbnb1 unbound: [72999:0] info: service stopped (unbound 1.9.1).
Jan 21 01:56:46 airbnb1 unbound: [72999:0] info: start of service (unbound 1.9.1).
Jan 21 01:56:46 airbnb1 unbound: [72999:0] info: service stopped (unbound 1.9.1).
Jan 21 01:56:54 airbnb1 unbound: [72999:0] info: start of service (unbound 1.9.1).
Jan 21 01:58:12 airbnb1 unbound: [72999:0] info: service stopped (unbound 1.9.1).
Jan 21 01:58:20 airbnb1 unbound: [72999:0] info: start of service (unbound 1.9.1).

I guess it's restarting when a dhcp lease is renewed.

The 10 second outage is being noticed by other clients on the network, particularly now that there is heavier usage. A 10 second outage of dns is the same as a 10 second internet outage for them.

Could unbound be reloaded, not restarted?

Actions
Copy link

Also available in: Atom PDF