dig

[Jerry]

On Thu, 22 Aug 2013 11:14:04 +1000
Colin House articulated:

> On 22/08/2013 9:34 AM, 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:
> >
> > dig freebsd.org +trace
> >
> > 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.
> 
> Have you tested against another NS?  I ran into a similar problem
> when setting up unbound as a local recursor recently on a 9.1-STABLE 
> (r251985) box.
> 
> dig +trace <domain> would return (next to) nothing.  dig +trace
> <domain> @8.8.8.8 worked as expected.
> 
> I found it was the access-control configuration of unbound.  Changing
> my "access-control: ::1 allow" to "access-control: ::1 allow_snoop" 
> restored the +trace functionality.
> 
> I'm not sure how this translates with bind.. Perhaps the defaults
> have changed between the versions that you're running (if you're
> running the base versions on 7.2 and 9.1) or your recursive server
> isn't allowing it on 9.2?  Fwiw, in unbound, "allow" allows recursive
> lookups, "allow_snoop" allows both recursive and non-recursive
> lookups.

$ dig freebsd.org +trace

; <<>> DiG 9.6.-ESV-R7-P2 <<>> freebsd.org +trace
;; global options: +cmd
;; Received 12 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms

$ drill freebsd.org +trace
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 28341
;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; +trace.      IN      A

;; ANSWER SECTION:
+trace. 10      IN      A       69.16.143.110
+trace. 10      IN      A       66.152.109.110

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 34 msec
;; SERVER: 209.18.47.62
;; WHEN: Thu Aug 22 06:35:54 2013
;; MSG SIZE  rcvd: 56

I was surprised at the difference between the output of the two
commands.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________