Deadwood 2.9.04 released

[Sam Trenholme]

> I am not aware of any hostnames that Deadwood can not resolve but
> other DNS servers can resolve.

Found one: www.bookride.com, but it’s aplus.net’s DNS servers giving
out the broken DNS packets that confused Deadwood:

$ dig @64.29.144.70 www.bookride.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @64.29.144.70
www.bookride.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10397
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;www.bookride.com. IN A

;; ANSWER SECTION:
www.bookride.com. 3600 IN CNAME ghs.google.com.

;; AUTHORITY SECTION:
google.com. 86400 IN SOA ns1.aplus.net. hostmaster.aplus.net. 1007
86403 3600 3600000 86400

;; Query time: 304 msec
;; SERVER: 64.29.144.70#53(64.29.144.70)
;; WHEN: Sat Aug 14 01:18:15 2010
;; MSG SIZE rcvd: 119

This is an invalid packet: It is marked as a NXDOMAIN (complete with a
SOA record in the NS/Authority section), but it is actually a CNAME.

I have updated Deadwood to treat these broken packets like ordinary
CNAME packets. The snapshot can be downloaded here:

http://maradns.org/deadwood/snap/

I also am trying to report this issue with aplus.net (I sent one
report, got the runaround, and have sent another email to the address
they referred me to).  I don’t know what product they use for
authoritative DNS, but it’s broken.

- Sam