Unbound 1.13.1 - Cannot resolve host

[Jaap Akkerhuis]

 Joe Abley via Unbound-users writes:

 > FreeBSD ports are not directly tied to FreeBSD releases.
 >
 > Jaap maintains the unbound port. The full commit history is public, so 
 > it's at least possible to track down precisely what commits introduced
 > and removed the typo, even if it's possibly not fun work to do.

For ports I hardly ever change the contents  release of the "upstreams"
so version numbers follow this case, the ones for unbound. I just
add the necessary scaffolding to make it a FreeBSD port. If the
change is documented, it will be in the Change Log for unbound (currently
<https://www.nlnetlabs.nl/projects/unbound/download/#unbound-1-13-1>).
And indeed, it seems mentioned for the release of unbound 1.4.7 (November 2010).

	jaap

 >
 > https://www.freshports.org/dns/unbound/
 > <https://www.freshports.org/dns/unbound/>
 >
 >
 > > On 29 Jun 2021, at 16:17, Fongaboo via Unbound-users
 > <unbound-users at lists.nlnetlabs.nl> wrote:
 > >
 > >
 > > What FreeBSD version had this snafu pray tell?
 > >
 > >
 > > On Mon, 28 Jun 2021, Robert Blayzor via Unbound-users wrote:
 > >
 > >> I actually finally tracked this down. It had to do with some old
 > options left in the FreeBSD port distro.
 > >>
 > >> The old distro had "private-address: 192.254.0.0/16" which should not
 > be there and was probably supposed to be "169.254.0.0/16".
 > >>
 > >>
 > >>
 > >> On 6/25/21 3:46 PM, Fongaboo via Unbound-users wrote:
 > >>> So I have confirmed I am getting SERVFAIL for that domain when
 > querying your unbound server. Was able to recreate success for dig
 > +trace and queries off of outside caching nameservers.
 > >>> But trying to figure out how dns2.p06.nsone.net is coming into play
 > in the logs. Otherwise not seeing anything jumping out at me that looks
 > real wrong.
 > >>> What happens after you run?: unbound-control flush_zone
 > bborganizing.com
 > >>> Even if it resolves after that, from what you've described, I guess
 > you'd have to keep an eye on it. Wondering if the zone is just getting
 > corrupted somehow?
 > >>
 > >>