From owner-freebsd-stable@freebsd.org Tue Aug 7 14:40:24 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 464AE106063C for ; Tue, 7 Aug 2018 14:40:24 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D6D8E720F9 for ; Tue, 7 Aug 2018 14:40:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9C5F3106063A; Tue, 7 Aug 2018 14:40:23 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B1131060639 for ; Tue, 7 Aug 2018 14:40:23 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2r.ore.mailhop.org (outbound2r.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 18E8C720F8 for ; Tue, 7 Aug 2018 14:40:22 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: c87a370d-9a4f-11e8-904b-1d2e466b3c59 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id c87a370d-9a4f-11e8-904b-1d2e466b3c59; Tue, 07 Aug 2018 14:40:09 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w77Ee8mp053311; Tue, 7 Aug 2018 08:40:08 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1533652808.9860.83.camel@freebsd.org> Subject: Re: How do I stop using local_unbound ? From: Ian Lepore To: Pete French , Kevin Oberman , John Kennedy Cc: "stable@freebsd.org" Date: Tue, 07 Aug 2018 08:40:08 -0600 In-Reply-To: <77911329-d91d-d76d-38cd-a2c96fb8c122@ingresso.co.uk> References: <20180806145717.GE30738@phouka1.phouka.net> <77911329-d91d-d76d-38cd-a2c96fb8c122@ingresso.co.uk> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Aug 2018 14:40:24 -0000 On Tue, 2018-08-07 at 15:35 +0100, Pete French wrote: > > > >     Hmm.  First, make sure that it isn't running (service local_unbound > >     stop, etc). > >     Then look at your /etc/resolv.conf -- unbound tends to rewrite that > >     on initial > >     startup, taking some of it's settings and inserting itself into the > >     middle as a > >     caching DNS server.  At the very least, you want something like this: > > > >              nameserver 8.8.8.8 > > > >     I think the default DHCP client stomps all over /etc/resolv.conf > >     fairly well, > Thats my problem - it doesnt rewrite it :-( I ended up taking one of my  > machines with a working unboudn setup, rysncing the files to the non  > working ones, re-enabling unbound and lettign it get on with its life.  > Have given up on removing it! > > Thanks for the advice though, I will dig into it on more detail when I  > have a moment. > > cheers, > > -pete. I wonder if OpenResolve is involved in rewriting the config. Do you have an /etc/resolvconf.conf file, and if so, does it contain configuration related to updating unbound? -- Ian