On Tue, Jul 17, 2001 at 12:09:46PM -0700, 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.
Yeah, "ne2k-pci" would be the right one for you then. Glad to hear you
found it.
> 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?
nslookup is part of 'dnsutils'... odd that it isn't installed. just
"apt-get install dnsutils" and all should be well. "nslookup" is rather
deprecated though: try "dig", you'll like it alot more once you get
the hang of it.
You do not need to run BIND to resolve names. I recommend running
BIND in a caching configuration, but you do not need to.
There are three keywords to remember with resolv.conf:
domain blenke.com
search blenke.com loft.blenke.com
nameserver 127.0.0.1
nameserver 10.0.0.4
nameserver 10.0.0.3
nameserver 10.0.0.2
The domain keyword specifies what the fqdn of YOUR host is.
The search keyword specifies domain suffix that automagically get
appended to DNS queries. Using the "search" keyword, you can "nslookup
ns" and have it resolv for ns.blenke.com, and ns.loft.blenke.com. The
downside: these suffixes are added to every resolution query and end
up causing more DNS traffic.
The nameserver keywords specify DNS nameservers that you wish to query
from, in order. I use 127.0.0.1 and run bind locally, so the latter
three are generally not needed (but are there just in case).
- Ian C. Blenke <icblenke@nks.net>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:11:45 EDT