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.