Re: How to resolve names



On Sun, 18 Mar 2007 17:56:35 +0100, Norbert Kolvenbach wrote:

Dear experts,

this is possibly a very dumb problem/question and that may be the reason I
do not get a resolution.

i have 3 Linux pc connected to the internet via WLAN DSL router. 2 are
conencted via WLAN one is directly connected via LAN cable. The router
uses DHCP to assign dynamic IP addresses.

So I can ping and try to ssh/telnet the 2 other machines from my PC via
ip-address (no supprise).

I cannot do it by using their host names although I get proper
name/address resolution via nslookup.

As it stands this doesn't add up. If ping etc. by IP works and nslookup of
the names works (nslookup is a broken and outdated tool BTW, you should
use dig instead, but its brokenness does not extend to returning answers
when none are available) then ping etc. by name should too.

I assume that the router is acting as the DNS server, can you confirm this?

What output/errors are issued when you:

ping <name>

dig <name>

host <name>

getent hosts <name>

?

Note that dig does not append the domain name specified in
/etc/resolv.conf, you have to include it in the command, i.e. dig
<host>.<domain>.

what is in /etc/resolv.conf? What does the "hosts:" entry in
/etc/nsswitch.conf read?

Regards, Ian
.



Relevant Pages

  • Re: slow start
    ... Should I be able to ping all the ntp servers in my /etc/ntp.conf? ... You should not, however, start your troubleshooting by pinging your NTP servers. ... Don't use nslookup, use dig. ... I suggested nslookup, rather than dig, because nslookup is installed on both Solaris and Windoze and I think Linux as well. ...
    (comp.protocols.time.ntp)
  • Re: ping
    ... > man nslookup ... > man dig ... "man ping" would seem, to me, to be more appropriate here. ... As long as *a* nameserver somewhere has the correct entries it'll work ...
    (comp.os.linux)
  • Dig and nslookup resolve; ping doesnt
    ... I'm able to resolve ... names such as www.yahoo.com using nslookup or dig but not using ping. ...
    (comp.os.linux.networking)
  • Re: SAM not installed by default on 11.0?
    ... Check that atlantis is actually in /etc/hosts. ... Use ping and nslookup ... to check status of name resolution. ...
    (comp.unix.admin)
  • Re: SAM not installed by default on 11.0?
    ... Check that atlantis is actually in /etc/hosts. ... Use ping and nslookup ... to check status of name resolution. ...
    (comp.sys.hp.hpux)