public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: ping: unknown host ?
Date: Tue, 20 Apr 2004 19:05:42 -0700	[thread overview]
Message-ID: <5.1.0.14.1.20040420184849.01efb810@celine> (raw)
In-Reply-To: <4085CBC7.9000908@gelm.net>

At 09:17 PM 4/20/2004 -0400, chuck gelm wrote:
>Howdy, Y'all:
>
>  My host, 'router', seems to not be resolving host names to IP addresses.
>
>  I can ping by IP address, but not by domain name. i.e.
>ping 206.141.251.2
>  is find, whereas
>ping gelm.net
>  fails with error:
>ping: unknown host gelm.net.
>
>This is my router (DSL<>LAN) and is functioning as the local
>domain name server, but cannot serve its self. ?
>
>Attached is the output of
>netstat -r
>route -n
>resolv.conf
>
>  What is not working?

Well, /etc/resolv.conf says that the router is to use 206.141.251.2 as a 
resolver. And you seem to say above that the router can ping that IP 
address, which tells us that routing to it is OK. Possibilities I can think 
of are:

1. What is 206.141.251.2 ? I'm surmising that it is your ISP's nameserver. 
Do you know that it is a working resolver (to ask the most basic detail 
question, does it ACCEPT traffic to port 53/UDP)?

2. Are you running any firewalling on your host that might be interfering 
with traffic to or from the resolver? Checking this is somewhat kernel 
specific; if you are running 2.4.x, then check with

         iptables -nvL
         iptables -t nat -nvL

It is quite possible that your default table DENYs or REJECTs DNS traffic 
to and from the router itself, while your nat table ACCEPTs it to and from 
LAN hosts.

3. HOW is the router "functioning as the local domain name server"? Is it 
running BIND (named)? dnscache? Something else? However it provides DNS to 
the LAN, you do not have it set up to use that method for itself, since the 
entry (below) in /etc/resolv.conf points to what I assume is an off-LAN 
nameserver.

One other detail: please ALWAYS report the routing table with "netstat 
-nr", or an equivalent that reports addresses, not names. YOU know what IP 
address network "localnet" translates too, but WE do not ... I've been 
assuming that this router NATs a private-address LAN (e.g., 
192.168.1.0/24), but your reporting by network name conceals that 
information. And if my guess is wrong, a lot else that I said could easily 
also be wrong.


>Chuck
>
>
>Kernel IP routing table
>Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
>68.254.31.254   *               255.255.255.255 UH        0 0          0 ppp0
>localnet        *               255.255.255.0   U         0 0          0 eth0
>loopback        *               255.0.0.0       U         0 0          0 lo
>default         68.254.31.254   0.0.0.0         UG        0 0          0 ppp0
>nameserver 206.141.251.2
>Kernel IP routing table
>Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
>68.254.31.254   0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
>192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
>127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
>0.0.0.0         68.254.31.254   0.0.0.0         UG    0      0        0 ppp0


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

      reply	other threads:[~2004-04-21  2:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 20:10 FW: Need help figurinig out rsync Eve Atley
2004-04-21  1:17 ` ping: unknown host ? chuck gelm
2004-04-21  2:05   ` Ray Olszewski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.1.20040420184849.01efb810@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox