anyone running djbdns?

[Robert La Ferla]

Ward Vandewege wrote:
> These work fine for me (I use djbdns/dnscache).
>
> Try this first
>
>   dig www.edmunds.com @216.255.129.249
>   dig www.edmunds.com @216.255.130.249
>
>   dig www.inifiniti.com @129.33.82.4
>   dig www.inifiniti.com @129.33.82.5
>
> If that does not work, you can't talk to the respective nameservers for the
> domain.
>
> If so, maybe you have ECN (Explicit Congestion Notification) enabled in your
> kernel? If those two hosts (or, actually, the nameserver(s)) for the domains
> are on a network/device that chokes on ECN, you might find their nameserver
> unreachable from your box.
>
>   cat /proc/sys/net/ipv4/tcp_ecn
>
> Returns 0 if disabled, or 1 if it is enabled. If it's 1, try
>
>   echo 0 >/proc/sys/net/ipv4/tcp_ecn
>
> and then try 
>   
>   dig www.edmunds.com @216.255.129.249
>   dig www.edmunds.com @216.255.130.249
>
>   dig www.inifiniti.com @129.33.82.4
>   dig www.inifiniti.com @129.33.82.5
>
> to see if that fixed it...
>
> Note that having ECN on is NOT wrong; in fact it's good for your network -
> smarter congestion control. But sadly there are still broken routers/hosts
> out there that can't cope with it...
>   
I don't have ECN enabled.  When I run those dig commands, I get a status 
of "REFUSED" back.

# dig www.edmunds.com @216.255.129.249

; <<>> DiG 9.1.3 <<>> www.edmunds.com @216.255.129.249
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 41115
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

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

;; Query time: 28 msec
;; SERVER: 216.255.129.249#53(216.255.129.249)
;; WHEN: Sat Jan 14 23:55:33 2006
;; MSG SIZE  rcvd: 33