Quote:>I'm running 3.03 Redhat linux, and when i key in 'dip -t' (or any kind
>of dip incantation) I get a 'Host name lookup failure'. Anyone have an
>idea on what I've done wrong?
(When I say 'mymachinename' I mean the name given to you by typing
"uname -n".)
Make sure the line:
order hosts,bind
is in your /etc/host.conf, and the line
<Your IP address> mymachinename.whatever.com mymachinename
is in your /etc/hosts file.
Dip should have no troubles with looking up your hostname after that.
If you're on a dynamic SLIP line and don't know your IP address
beforehand... um... run and hide, I guess. One way around the problem
might to be to change the line in /etc/hosts that looks like:
127.0.0.1 localhost
to read:
127.0.0.1 localhost mymachinename
Then when DIP looks up the address of "mymachine," it'll get back
"127.0.0.1" and go along on it's merry way. I'm not sure DIP really
cares what result it gets back. But it surely will fall over and die
if it gets no result back. So you just kind of fool DIP by giving it
a "dummy" value when it asks.
This might be a workable kludge; however, it may cause unforseen problems,
too. I'm not entirely sure. It does work for me. Try it. If it works for you
also, then great. If not, you might want to look into setting up a small,
cache-only nameserver. It's kind of a pain, and perhaps a bit overkill, but
it seems to cure just about any woes you might be having with hostname lookup
failures.
-Ben
--
"BGC: Because some of us believe women over 14 are still *."
=--------- http://www.veryComputer.com/~cantrick/home.html -------------=
*Ben Cantrick, diehard BGC otaku and Priss fan. ---> THE BGC DUBS SUCK! <---*
*Mac? Ha. "When I want to spend 50% of my time fighting an OS, I'll use VMS."*