Hello,

I just installed Suse 10.1 on an AMD 64 system at work. I am unable to ping LAN nodes in our local domain. Windows XP works fine, and FreeBSD pings everybody just fine. The firewall is turned off, and it appears I have DNS servers set up properly.

Regards,

Randy.

can you prove these things? show us /etc/resolve.conf, proof of successful name resolution, a traceroute to, for example, google.com

Here is a copy of resolv.conf. I may not have mentioned, DNS works on the internet. It doesn't work internally. The Suse system is using DHCP just like the windows clients. It is pointing to the same internal DNS servers.

Regards,

Randy.

### BEGIN INFO
#
# Modified_by: dhcpcd
# Backup: /etc/resolv.conf.saved.by.dhcpcd.eth0
# Process: dhcpcd
# Process_id: 6995
# Script: /sbin/modify_resolvconf
# Saveto:
# Info: This is a temporary resolv.conf created by service dhcpcd.
# The previous file has been saved and will be restored later.
#
# If you don't like your resolv.conf to be changed, you
# can set MODIFY_{RESOLV,NAMED}_CONF_DYNAMICALLY=no. This
# variables are placed in /etc/sysconfig/network/config.
#
# You can also configure service dhcpcd not to modify it.
#
# If you don't like dhcpcd to change your nameserver
# settings
# then either set DHCLIENT_MODIFY_RESOLV_CONF=no
# in /etc/sysconfig/network/dhcp, or
# set MODIFY_RESOLV_CONF_DYNAMICALLY=no in
# /etc/sysconfig/network/config or (manually) use dhcpcd
# with -R. If you only want to keep your searchlist, set
# DHCLIENT_KEEP_SEARCHLIST=yes in /etc/sysconfig/network/dhcp or
# (manually) use the -K option.
#
### END INFO
search stva.local
nameserver 10.2.1.252
nameserver 10.2.1.80

ahh so it's internal stuff that's failing... so... have you even got an internal dns server?

Yes we have DNS servers internally. They work on FreeBSD, Windows XP, Windows NT, Windows 2003, and every distribution we have except my lowly IT computer running SUSE. I must be doing something wrong! I am using DHCP like the rest of the operating systems are.