Date:        Fri, 15 Aug 2003 10:01:11 -0700 (PDT)
    From:        "Jeremy C. Reed" <reed@reedmedia.net>
    Message-ID:  <Pine.LNX.4.43.0308150957320.11471-100000@pilchuck.reedmedia.net>

  | By default, (just like FreeBSD) it will use the /etc/resolv.conf file.
  | 
  | Make sure that the format is correct:
  | 
  | nameserver 192.168.0.1
  | 
  | (replace the IP above with the IP of your nameserver)
  | 
  | Don't use a hostname; use an IP address.

Yes, all of that, as well as making sure resolv.conf is readable, / and
/etc have the x bit set for everyone, ...  (ie; make sure that /etc/resolv.conf
has a correctly formatted "nameserver" line that all users are able to
see (like using cat /etc/resolv.conf)).

You should also probably make sure that there is essentially no extraneous
noise in resolv.conf - the resolver generally just ignores anything that
it fails to understand, but there are probably exceptions...

  | Make sure you have connectivity to that IP address. (Is your networking
  | working?)

That won't be relevant however, that might cause DNS lookups to fail,
but it wouldn't cause them to be sent to 0.0.0.0

Nor can this

  | Have you ever modified your /etc/nsswitch.conf?

be relevant, if the resolver routines are attempting to contact a
local nameserver, then clearly the dns entry is in nsswitch.conf, or
there would be no DNS related activity at all.

kre