dig +trace question

[Nico Cartron]

Are you sure it's not your setup?
I have plenty of dig running on FreeBSD (with bind-utils 9.14) and also Debian and they work just fine. 

-- 
Nico

> On 21 Jun 2019, at 09:14, Ronald F. Guilmette <rfg at tristatelogic.com> wrote:
> 
> In message <9BA154CC-2272-46EC-A793-47FF31DCA418 at arin.net>, you wrote:
> 
>> Hi Ronald,
>> You usually need to reinstall packages and ports after you do a major
>> version upgrade to FreeBSD.
> 
> I guess that I did not make myself clear.  Everything on this system is
> freshly installed, from scratch.
> 
> I have the FreeBSD package "bind-tools-9.12.4P1" installed.... the latest,
> undoubtedly compiled against FreeBSD 12.0.
> 
> Anyway, it really does appear now that this problem *is* a regression in
> dig, and that it's not just me.
> 
> I tried my dig with both +trace -and -x also on *two* different Ubuntu
> system I have here.
> 
> On Ubuntu 16.04 LTS it works as expected.
> 
> On Ubuntu 18.04 LTS it fails as I have reported.
> 
> It looks to me like somebody broke dig.
> 
> Where do I file the formal bugreport?
> 
> 
> Regards,
> rfg
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users