From owner-freebsd-questions@freebsd.org Sun Nov 13 20:53:53 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4F9EC406E8 for ; Sun, 13 Nov 2016 20:53:53 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "*.xs4all.nl", Issuer "GlobalSign Domain Validation CA - SHA256 - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AB38120D for ; Sun, 13 Nov 2016 20:53:52 +0000 (UTC) (envelope-from mbeis@xs4all.nl) Received: from yokozuna.lan ([83.160.85.125]) by smtp-cloud6.xs4all.net with ESMTP id 7Yti1u0072iF10301Ytjj8; Sun, 13 Nov 2016 21:53:43 +0100 Received: from localhost (localhost [IPv6:0:0:0:0:0:0:0:1]) by yokozuna.lan (8.15.2/8.15.2) with ESMTPS id uADKrfho002129 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 13 Nov 2016 21:53:42 +0100 (CET) (envelope-from mbeis@xs4all.nl) Date: Sun, 13 Nov 2016 21:53:41 +0100 (CET) From: Marco Beishuizen X-X-Sender: marco@localhost Reply-To: Marco Beishuizen To: Polytropon cc: freebsd-questions@freebsd.org Subject: Re: unbound forward.conf gets overwritten In-Reply-To: <20161113214249.4834e89f.freebsd@edvax.de> Message-ID: References: <20161113214249.4834e89f.freebsd@edvax.de> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2016 20:53:53 -0000 On Sun, 13 Nov 2016, the wise Polytropon wrote: > If I remember correctly, /var/unbound content is getting generated > automatically, so changes to those files will not survive a reboot. > Check "man unbound.conf" on how to set the forward-addr options in the > ("static") configuration file. At service (re)start, those should cause > the required settings in /var/unbound/forward.conf to appear. I've found a solution already: comment out the line "unbound_conf="/var/unbound/forward.conf"" in /etc/resolvconf.conf. At first I tried to add the forward-addr lines in unbound.conf, but that doesn't work. Why the forward.conf file gets overwritten every reboot by default is unclear. Regards, Marco -- The reason why worry kills more people than work is that more people worry than work.