Yeah, I bet that the permissions are probably the problem with
resolv.conf, as I created it while running as root. I won't be able to
tell until tomorrow when I get to work and can mess with the machine,
but that is probably it.
--Kevin Fogleman
Robert Haeckl wrote:
>
> Your on the right track with /etc/resolv.conf. No, you don't need Bind
> (named) running. The resolver routines will check for nameservers in
> the /etc/resolv.conf file. The records should be in the form:
>
> nameserver xxx.xxx.xxx.xxx
> nameserver xxx.xxx.xxx.xxx
> search isp.domain.name
>
> Processes cache the resolv.conf configuration for their life so start a
> new app when you check. Did you check the permissions on the
> resolv.conf file (644)? I presume you have already checked that you can
> ping addresses.
>
> -Robert
>
> Electric Monk wrote:
> >
> > OK, after going through /proc/pci, I found out that
> > the card is actually an NE200-PCI card (so much for
> > advertising!), and I installed the appropriate driver,
> > and the network interface seems to work now.
> >
> > However, now I have an entirely different problem: I
> > can't resolve hostnames to addresses. Debian also
> > apparently does NOT install nslookup in its base
> > package, so I'm going to have to dig that up off the
> > CD. /etc/resolv.conf wasn't already present, so I
> > created it using 'man resolv.conf' as my guide, with
> > both of my ISP's DNS servers' addresses entered, but I
> > am still unable to resolve names. Do I need to be
> > running BIND in order to resolve names?
> >
> > --Kevin Fogleman
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:11:57 EDT