Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Suse 10 SP3 won't ping hostname Post 302445747 by kopper on Monday 16th of August 2010 06:08:56 PM
Old 08-16-2010
Quote:
Originally Posted by methyl
Googling "ipv6-mcastprefix" and "ping" makes me realise that this is a common problem with Suse Linux. Finding a sensible fix amongst the sheer volume of posts is not going to be easy.

Surprised that you haven't had an answer here:
Suse 10 SP3 won't ping hostname


I'm backing off from this one because Suse is not "normal".
Good luck with finding a specialist.

thanks a lot that was the issue
Name Resolution Problems with ".local" Domains

Name Resolution Problems with ".local" Domains

Situation

Applications or system programs likepinghave problems with the resolution of names in a DNS domain ending with .local.

For example, when you try to test the connection to a machine called runner in your organisation's acme.local domain with the command ping runner or ping runner.acme.local, you get an ERROR: unknown host runner.acme.local even though you can look up that host name with dig runner.acme.local, or it takes longer than expected for the pinging to start.

Resolution

Set

mdns off
in the resolver configuration file/etc/host.conf. This option, introduced in SLES9 Service Pack 1, disables the special handling of the top-level domain .local by the resolver: it instructs the resolver not to use multicast DNS, but to use the more common unicast DNS instead.
This solution addresses this specific problem. To prevent similar problems in the future, we recommend using official DNS names for your network, as top-level domains that are currently unassigned may be assigned for special purposes in the future, as has happened with .local.
 

9 More Discussions You Might Find Interesting

1. HP-UX

UX 11iV2 - No ping by hostname

Hi. I just installed the HP-UX 11i V2. I have problems with CDE - it is inoperative (after logon there is a message box: messaging system failure - or something like that, it asks to check /etc/hosts and network settings). nslookup works by hostname and IP, hostname shown the correct... (7 Replies)
Discussion started by: netwalker
7 Replies

2. Solaris

cannot ping by hostname

Hi All, My current setup is: 1x Windows Server (Windows 2000 server) 1x Unix Server 2x Windows machine 3x Unix Terminals (Hostnames = A, B and C) Problem The problem iam having is Unix terminal C cannot be ping across by Unix terminal A or B or Unix server by using the hostname. Unix... (1 Reply)
Discussion started by: tlee
1 Replies

3. Solaris

Can't ping using hostname on Solaris 10

I recently installed Solaris 10 on my Sun workstation. I cannot ping using hostname from another computer on the same network. But I can ping using the IP address. Also I can ping other systems using their hostnames. Can anyone give some information regarding how to resolve this issue. (4 Replies)
Discussion started by: alpha123
4 Replies

4. AIX

Ping by hostname

Hello everyone I have a partition with a problem with ping. If I do a ping by ip for example ping 1.1.1.1 I got no problem but If I ping by hostname for example ping partition1 take almost a minute to respond me. I have Aix 5.3 and I have another 19 partitions with no problem. The only... (5 Replies)
Discussion started by: lo-lp-kl
5 Replies

5. UNIX for Dummies Questions & Answers

Suse Ent 10 SP3 won't boot

hi I have Suse Ent 10 SP3 that when I reboot the server sometimes it won't... it behaves like this up and running If I rebooted boots ok so up and running again and If I rebooted again it won't from Hadr Drives What I can check on my boot/grub? why sometimes boots OK and sometimes does... (0 Replies)
Discussion started by: karlochacon
0 Replies

6. UNIX for Advanced & Expert Users

ping by hostname not working

anyone ever seen this problem: I can ping the server by IP address but I can't by hostname. nslookup is working and dns query is ok. # nslookup mwxnsb24 Server: 10.11.49.206 Address: 10.11.49.206#53 Name: mwxnsb24 Address: 10.10.58.175 # ping... (8 Replies)
Discussion started by: linuxgeek
8 Replies

7. Solaris

my sun solaris 10 cannot ping and nslookup other server using hostname.

hi.... i have sun solaris 10 server, fedora 10, and Windows Server.. i cant ping my sun solaris 10, fedora 10 and Windows Server using hostname (etc: ping winserver.bengkel2.com), but i can ping all using IPV4 and IPV6 address.. can u give some suggestion to solve my problem or some idea to... (3 Replies)
Discussion started by: izuan_7657
3 Replies

8. Shell Programming and Scripting

Ping the hostname of many servers using a script

Hi We have some 300 servers in the Data center and some of them are running with AIX and some of them are running with Solaris. I need a script which can be run in one of the server and that script should ping the hostname of all the 300 servers. Also the script should notify if any server is... (9 Replies)
Discussion started by: newtoaixos
9 Replies

9. IP Networking

DNS problem : ping doesn't recognize hostname

I have vmware on my windows PC ( hostname : acer ). vmware has RHEL 7 ( hostname : rhel7 ) installed recently. RHEL IP configuration IP : 192.168.5.128 Netmask : 255.255.255.0 ssh to rhel7 works from acer using putty resolve.conf cat /etc/resolv.conf nameserver 192.168.5.1 host... (12 Replies)
Discussion started by: hiten.r.chauhan
12 Replies
RESOLVER(5)							File Formats Manual						       RESOLVER(5)

NAME
resolver - resolver configuration file SYNOPSIS
/etc/resolv.conf DESCRIPTION
The resolver is a set of routines in the C library (resolv(3)) that provide access to the Internet Domain Name System. The resolver con- figuration file contains information that is read by the resolver routines the first time they are invoked by a process. The file is designed to be human readable and contains a list of keywords with values that provide various types of resolver information. On a normally configured system this file should not be necessary. The only name server to be queried will be on the local machine, the domain name is determined from the host name, and the domain search path is constructed from the domain name. The different configuration options are: nameserver Internet address (in dot notation) of a name server that the resolver should query. Up to MAXNS (currently 3) name servers may be listed, one per keyword. If there are multiple servers, the resolver library queries them in the order listed. If no nameserver entries are present, the default is to use the name server on the local machine. (The algorithm used is to try a name server, and if the query times out, try the next, until out of name servers, then repeat trying all the name servers until a maximum number of retries are made). domain Local domain name. Most queries for names within this domain can use short names relative to the local domain. If no domain entry is present, the domain is determined from the local host name returned by gethostname(2); the domain part is taken to be everything after the first `.'. Finally, if the host name does not contain a domain part, the root domain is assumed. search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it begins with the local domain name, then successive parent domains that have at least two components in their names. This may be changed by listing the desired domain search path following the search keyword with spaces or tabs separating the names. Most resolver queries will be attempted using each component of the search path in turn until a match is found. Note that this process may be slow and will gen- erate a lot of network traffic if the servers for the listed domains are not local, and that queries will time out if no server is available for one of the domains. The search list is currently limited to six domains with a total of 256 characters. The domain and search keywords are mutually exclusive. If more than one instance of these keywords is present, the last instance will override. The keyword and value must appear on a single line, and the keyword (e.g. nameserver) must start the line. The value follows the keyword, separated by white space. FILES
/etc/resolv.conf SEE ALSO
gethostbyname(3N), resolver(3), hostname(7), named(8) Name Server Operations Guide for BIND 4th Berkeley Distribution December 14, 1989 RESOLVER(5)
All times are GMT -4. The time now is 02:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy