Date: Wed, 21 Aug 2013 17:03:35 -0700 From: Doug Hardie <bc979@lafn.org> To: Frank Leonhardt <frank2@fjl.co.uk> Cc: "freebsd-questions@freebsd.org List" <freebsd-questions@freebsd.org> Subject: Re: dig Message-ID: <44733A0D-5BAD-43B9-B154-554A35260089@lafn.org> In-Reply-To: <C0F6AD69-C3BF-4E0E-B72D-88CE6ACE6C67@lafn.org> References: <F6FFC04A-5942-4ED8-BF33-C683EB07C798@lafn.org> <5215514F.4030303@fjl.co.uk> <C0F6AD69-C3BF-4E0E-B72D-88CE6ACE6C67@lafn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 August 2013, at 17:02, Doug Hardie <bc979@lafn.org> wrote: >=20 > On 21 August 2013, at 16:46, Frank Leonhardt <frank2@fjl.co.uk> wrote: >=20 >> On 22/08/2013 00:34, Doug Hardie wrote: >>> There appears to be a problem with dig and the +trace option in 9.2. = I believe its also in 9.1. The command: >>>=20 >>> dig freebsd.org +trace >>>=20 >>> Only yields a dumb response. No useful information is provided. = Running the same command on FreeBSD 7.2 yields a complete trace with = lots of useful information. >>> _______________________________________________ >>>=20 >>=20 >> Works for me on 9.0 and 9.1 (and 8.2, 7.1, 7.0) >>=20 >> Is there something wrong with your local bind configuration? >>=20 >> Regards, Frank. >=20 > No. The 7.2 config is identical to the 9.1 and there is no bind = running on the 9.2. >=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44733A0D-5BAD-43B9-B154-554A35260089>