anyone running djbdns?

[Ward Vandewege]

On Sat, Jan 14, 2006 at 06:53:26PM -0500, Robert La Ferla wrote:
> I have an odd problem with djbdns.  A couple of common hosts (and I 
> suspect others) don't resolve but nearly everything else works fine and 
> has for years.  This problem has existed for years but I never took the 
> time to fix it.  I want to fix it!
> 
> e.g.
> 
> These don't work:
> 
> # host www.edmunds.com
> ;; connection timed out; no servers could be reached
> # host www.infiniti.com
> ;; connection timed out; no servers could be reached

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...

Ward.

> Yet most work:
> 
> # host news.bbc.co.uk
> news.bbc.co.uk. is an alias for newswww.bbc.net.uk.
> newswww.bbc.net.uk. has address 212.58.240.143
> 
> # host www.boston.com
> www.boston.com. has address 66.151.183.21
> www.boston.com. has address 66.151.183.31
> 
> Here are the ROOT servers:
> 
> # cat ...dnscache/root/servers/@
> 198.41.0.4
> 192.228.79.201
> 192.33.4.12
> 128.8.10.90
> 192.203.230.10
> 192.5.5.241
> 192.112.36.4
> 128.63.2.53
> 192.36.148.17
> 192.58.128.30
> 193.0.14.129
> 198.32.64.12
> 202.12.27.33
> 
> What could be the problem?  How do I go about diagnosing this?
> 
> Thanks!
> 

-- 
Pong.be         -(   Economic advantage is not in and of itself a valid    )-
Virtual hosting -( purpose or justification for copyright or patent laws.  )-
http://pong.be  -(                                                         )-
GnuPG public key: http://gpg.dtype.org