Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Jul 2020 12:36:28 -0700
From:      Doug Hardie <bc979@lafn.org>
To:        User Questions <freebsd-questions@freebsd.org>, Jerry <jerry@seibercom.net>
Subject:   Re: Problem with unbound resolving host
Message-ID:  <35DC599D-F342-4694-BA4D-8ED54137F27D@mail.sermon-archive.info>
In-Reply-To: <20200714194600.0fb4ed86@scorpio.seibercom.net>
References:  <20200713102451.017682d2@scorpio.seibercom.net> <44lfjmawcs.fsf@Be-Well.Ilk.Org> <20200714194600.0fb4ed86@scorpio.seibercom.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> On 14 July 2020, at 16:46, Jerry <jerry@seibercom.net> wrote:
>=20
> On Tue, 14 Jul 2020 12:34:59 -0400, Lowell Gilbert stated:
>>> FreeBSD 11.4-RELEASE-p1
>>>=20
>>> I have: local_unbound_enable=3D"YES" in my /etc/rc.conf file. The
>>> problem is with some utility programs like "curl" or "wget"
>>>=20
>>> When using either program to assess "https://www.spamhaus.org" a
>>> failure message is emitted similar to the following:
>>>=20
>>> curl https://www.spamhaus.org
>>> curl: (6) Could not resolve host: www.spamhaus.org
>>>=20
>>> The "nameserver" is set to "127.0.0.1" when that occurs. If I modify
>>> it as shown below to "192.168.1.1" everything works fine.
>>>=20
>>> nameserver 192.168.1.1
>>> options edns0 =20
>>=20
>> I'm sure that is in resolv.conf, but you should mention things like
>> that.
>>=20
>> I'm also assuming that the machine you're trying this on actually has
>> the address 192.168.1.1. Otherwise, um, yes, that's what should =
happen.
>>=20
>> Check if you're specifying "interface:" in your unbound.conf file. If
>> you do, you want to include 127.0.0.1 in the set you specify.  =
However,
>> unless you have a good reason, don't override it at all.
>>=20
>> Be well.
>=20
> The router's address is "192.168.1.1". The machine's address is
> "192.168.1.101". After every reboot, the address in the resolv.conf
> file is reset to 127.0.0.1, which usually works, but not always.
>=20
> This problem only started after updating from FreeBSD 11.4-RELEASE-p0
> to "p1". I have no idea what that could have done though.

I had the same problem a year or so ago.  It was consistent on all =
devices, although the problem domains tended to be different on each =
device.  I thought it was my provider's DNS and called them.  They sent =
out a tech who had just corrected a similar problem earlier that day.  =
He replaced my modem/router and the problem went away.  In my situation, =
resolving the problem domains using the modem/router's internal client =
worked fine.  Using my clients didn't.  Using 8.8.8.8 worked =
consistently from all.

-- Doug





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?35DC599D-F342-4694-BA4D-8ED54137F27D>