"Resolving" problem.

Hello.

The problem is (on my RH 7.3) that when i execute
e.g.: ping google.com, i get: ping: unknown host google.com.

"nslookup onet.pl" show in a few seconds:
;; connection timed out; no servers could be reached

When I ping some host by numeric IP, everything is OK.


Some of my configuration files:
/etc/host.conf:
order bind,hosts
multi on

/etc/hosts
127.0.0.1 serwerek localhost.localdomain localhost

/etc/resolv.conf
nameserver 194.204.159.1


Please, help me.

Robot.

Trix wrote:

> Hello.
>
> The problem is (on my RH 7.3) that when i execute
> e.g.: ping google.com, i get: ping: unknown host google.com.
>
> "nslookup onet.pl" show in a few seconds:
> ;; connection timed out; no servers could be reached
>
> When I ping some host by numeric IP, everything is OK.
>
>
> Some of my configuration files:
> /etc/host.conf:
> order bind,hosts
> multi on
>
> /etc/hosts
> 127.0.0.1 serwerek localhost.localdomain localhost

You need to return this line to its original form:

127.0.0.1 localhost.localdomain localhost

> /etc/resolv.conf
> nameserver 194.204.159.1

So ping the nameserver using its address:

$ ping 194.204.159.1

Does it respond? If it does not respond, that is your problem -- the
nameserver is unreachable. And check -- is that really the address of your
name server?

--
Paul Lutus
http://www.arachnoid.com

> So ping the nameserver using its address:
>
> $ ping 194.204.159.1
>
> Does it respond? If it does not respond, that is your problem -- the
> nameserver is unreachable. And check -- is that really the address of your
> name server?

Thanks for your answer.
I`ve changed everything you told me.
I`m not able to ping my nameserver by: ping 194.204.159.1 (when
I executed that command, nothing would be shown on the screen).
I executed ping 194.204.159.1 from my Windows connected
to my RH.7.3 server and it worked.
So, ping 194.204.159.1 doesn`t work on my server, but it works
on my workstation connected to my server.
194.204.159.1 is correct nameserver address -- the same I have
set on my second Windows and Linux box.

What to do next?
I`d like to thank You for your help.


Robot.

Trix wrote:

>> So ping the nameserver using its address:
>>
>> $ ping 194.204.159.1
>>
>> Does it respond? If it does not respond, that is your problem -- the
>> nameserver is unreachable. And check -- is that really the address of
>> your name server?
>
> Thanks for your answer.
> I`ve changed everything you told me.
> I`m not able to ping my nameserver by: ping 194.204.159.1 (when
> I executed that command, nothing would be shown on the screen).
> I executed ping 194.204.159.1 from my Windows connected
> to my RH.7.3 server and it worked.
> So, ping 194.204.159.1 doesn`t work on my server, but it works
> on my workstation connected to my server.
> 194.204.159.1 is correct nameserver address -- the same I have
> set on my second Windows and Linux box.
>
> What to do next?

You have no network connectivity. There is not nearly enough information in
your posts to go beyond this.

--
Paul Lutus
http://www.arachnoid.com

> You have no network connectivity. There is not nearly enough information
in
> your posts to go beyond this.
>
When i ping some host by its number IP, it doesn`t work. But when I
e.g. use "lynx" with the same number IP, everything works right.

Trix.

The second thing is that I can`t ping my DNS by its IP number, but
I can connect with use of telnet on port 53.

R.

Trix wrote:
> The second thing is that I can`t ping my DNS by its IP number, but
> I can connect with use of telnet on port 53.
>
> R.
>
>
What does your /etc/nsswitch.conf file look like?

Try: egrep "passwd|group" /etc/nsswitch.conf

#

# /etc/nsswitch.conf

#

# An example Name Service Switch config file. This file should be

# sorted with the most-used services at the beginning.

#

# The entry '[NOTFOUND=return]' means that the search for an

# entry should stop if the search in the previous entry turned

# up nothing. Note that if the search failed due to some other reason

# (like no NIS server responding) then the search continues with the

# next entry.

#

# Legal entries are:

#

# nisplus or nis+ Use NIS+ (NIS version 3)

# nis or yp Use NIS (NIS version 2), also called YP

# dns Use DNS (Domain Name Service)

# files Use the local files

# db Use the local database (.db) files

# compat Use NIS on compat mode

# hesiod Use Hesiod for user lookups

# [NOTFOUND=return] Stop searching if not found so far

#

# To use db, put the "db" in front of "files" for entries you want to be

# looked up first in the databases

#

# Example:

#passwd: db files nisplus nis

#shadow: db files nisplus nis

#group: db files nisplus nis

passwd: files nisplus

shadow: files nisplus

group: files nisplus

#hosts: db files nisplus nis dns

hosts: files dns nisplus

# Example - obey only what nisplus tells us...

#services: nisplus [NOTFOUND=return] files

#networks: nisplus [NOTFOUND=return] files

#protocols: nisplus [NOTFOUND=return] files

#rpc: nisplus [NOTFOUND=return] files

#ethers: nisplus [NOTFOUND=return] files

#netmasks: nisplus [NOTFOUND=return] files

bootparams: nisplus [NOTFOUND=return] files

ethers: files

netmasks: files

networks: files

protocols: files nisplus

rpc: files

services: files nisplus

netgroup: files nisplus

publickey: nisplus

automount: files nisplus

aliases: files nisplus

Trix wrote:
> # /etc/nsswitch.conf
> passwd: files nisplus
> shadow: files nisplus
> group: files nisplus
> hosts: files dns nisplus

Do you have root on this box? It might be useful to run a tcpdump on
your outgoing interface to see if the UDP traffic is getting out. In
reviewing your other posts, all of the tests that were successful were
TCP based (telnet port 25, lynx.)

You may want to get rid of the nisplus lines unless you are in an NIS+
environment. I don't think they'll cause any problems, but are unecessary.

Is it possible that your ISP is filtering UDP traffic?

Maybe try a 'traceroute -n 129.42.17.99' (www.ibm.com)