Problem with unbound resolving host

Arthur Chance freebsd at
Thu Jul 16 08:07:35 UTC 2020

On 15/07/2020 00:46, Jerry wrote:
> On Tue, 14 Jul 2020 12:34:59 -0400, Lowell Gilbert stated:
>>> FreeBSD 11.4-RELEASE-p1
>>> I have: local_unbound_enable="YES" in my /etc/rc.conf file. The
>>> problem is with some utility programs like "curl" or "wget"
>>> When using either program to assess "" a
>>> failure message is emitted similar to the following:
>>> curl
>>> curl: (6) Could not resolve host:
>>> The "nameserver" is set to "" when that occurs. If I modify
>>> it as shown below to "" everything works fine.
>>> nameserver
>>> options edns0  
>> I'm sure that is in resolv.conf, but you should mention things like
>> that.
>> I'm also assuming that the machine you're trying this on actually has
>> the address Otherwise, um, yes, that's what should happen.
>> Check if you're specifying "interface:" in your unbound.conf file. If
>> you do, you want to include in the set you specify.  However,
>> unless you have a good reason, don't override it at all.
>> Be well.
> The router's address is "". The machine's address is
> "". After every reboot, the address in the resolv.conf
> file is reset to, which usually works, but not always.

If /etc/resolv.conf is being reset every time you reboot, it sounds like
resolvconf(8) is running. What's in /etc/resolvconf.conf?

> This problem only started after updating from FreeBSD 11.4-RELEASE-p0
> to "p1". I have no idea what that could have done though.

Fat Earther: One who believes the world is round but has put on too
much weight round the middle.

More information about the freebsd-questions mailing list