Re: [MaraDNS list] Deadwood timing out on lookup

Of course, your example is incomplete since you are querying the cache (0 msec). For any tests that you do, you need to clear the cache so it goes out of your network. My other email might shed some light on a potential explanation. At least a guess!
 
Steve


----- Original Message -----
From: Sam Trenholme <[email protected]>
To: maradns list <[email protected]>
Cc: 
Sent: Saturday, August 6, 2011 2:05 AM
Subject: Re: [MaraDNS list] Deadwood timing out on lookup

[Messages sent to me by accident are forwarded to the list]

What messages do you get if you add the following to your dwood3rc:

verbose_level = 1000

To add this line, use an editor:

nano -w /etc/dwood3rc

Or, more simply:

echo verbose_level=1000 >> /etc/dwood3rc

You can then either run Deadwood via Duende and see all the messages
in /var/log/messages, or just run Deadwood directly from the shell and
see all of the messages on stdout.

Both the yahoo example works for me, as well as the TXT record for
84.211.52.72.list.dnswl.org.  Again, I am not, repeat not seeing this
problem, even on a nearly identical OpenVZ system.  Unfortunately,
until I can reproduce it on my setup, I will have to mark this bug as
"works for me, unreproducible"  Everything works fine even when using
Deadwood as a fully recursive resolver:

[set@cartomancy ~]$ dig @127.0.0.1 -t txt 84.211.52.72.list.dnswl.org

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @127.0.0.1 -t txt
84.211.52.72.list.dnswl.org
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33156
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;84.211.52.72.list.dnswl.org.   IN      TXT

;; AUTHORITY SECTION:
list.dnswl.org.         43200   IN      SOA     ns0.dnswl.org.
admins.dnswl.org. 1312582870 3600 300 432000 43200

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Aug  6 01:59:31 2011
;; MSG SIZE  rcvd: 92

- Sam