Suse 10 SP3 won't ping hostname

karlochacon · 08-13-2010, 10:16 PM

hi guys

I got something I haven't been able to fix
I configure a Linux Suse 10 box, added static IP, DNS (resolv), gateway (routes) but I am not able to ping other servers by name but nslookup works and the server can navigate on internet
check below
the problematic server is server-host20

Code:

# ping server-host1
ping: unknown host server-host1

# nslookup
> server-host1
Server:         192.168.1.2
Address:        192.168.1.2#53

Name:   server-host1.devmachines.com
Address: 192.168.1.20

other server can ping that server by name just fine

all my network information
by the way my server can ping DNS server by name just ok and as you see nslookup works

Code:

cat /etc/hosts
127.0.0.1       localhost.dominio.local localhost

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts
192.168.1.101   server-host20.devmachines.com

---------------------
#cat /etc/resolv.conf
nameserver 192.168.1.2
nameserver 192.168.1.3
search devmachines.com


# cat routes
192.168.1.15 - -

-------------------------------
# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth3
link-local      *               255.255.0.0     U     0      0        0 eth3
loopback        *               255.0.0.0       U     0      0        0 lo
default         192.168.1.15    0.0.0.0         UG    0      0        0 eth3

any idea guys?

thanks a lot

AlucardZero · 08-13-2010, 10:34 PM

/etc/nsswitch.conf

Code:

hosts: files dns

karlochacon · 08-13-2010, 11:05 PM

Quote:

Originally Posted by AlucardZero

/etc/nsswitch.conf

Code:

hosts: files dns

it is configured as you say

Code:

# passwd: files nis
# shadow: files nis
# group:  files nis

passwd: compat
group:  compat

hosts:          files dns
networks:       files dns

services:       files
protocols:      files
rpc:            files
ethers:         files
netmasks:       files
netgroup:       files nis
publickey:      files

bootparams:     files
automount:      files nis
aliases:        files

karlochacon · 08-16-2010, 11:07 AM

any other idea guys?

Gaidheal · 12-02-2011, 06:21 AM

Sorry to wake the dead, but I had this exact same issue after patching from SuSE SLES 10 SP2 to SP3 and had one server out of 50 that would *not* resolve, even after a complete redo of the network info through YaST2.

Turns out the /etc/resolv.conf file had the format listed below:

Quote:

Originally Posted by karlochacon

hi guys

Code:

---------------------
#cat /etc/resolv.conf
nameserver 192.168.1.2
nameserver 192.168.1.3
search devmachines.com

All my other servers (that worked) had the following format:
domain devmachines.com
nameserver 192.168.1.2
nameserver 192.168.1.3

Switched it on the problematic server, flushed the DNS cache and it worked.

Hope this helps someone.

Jamie