On Sat, 14.10.06 23:11, Walter Hofmann ([EMAIL PROTECTED]) wrote:
> > DO NOT USE "search local" UNLESS YOU REALLY KNOW WHAT YOU DO! And if
> > you do use it, don't file bugs about it. I am fully aware that it is
> > problematic.
>
> I read between the lines that the .local domain is something sp
On Sat, Oct 14, 2006 at 10:10:15PM +0200, Lennart Poettering wrote:
>
> As I already wrote in my last email, the "search local" is indeed the
> problem.
>
> It is explicitly *not recommended* to use "search local". If people
> choose to use it it's their problem.
>
> "search local" has lots of p
Walter Hofmann wrote:
> First, to answer your questions:
>
> - ping is netkit-ping 0.10-10.3.
> - a full strace of the failing ping (as root) is below
>
> My own theory:
>
> - It is not a problem with ping, other programs fail as well.
> - It fails after trying to send to 224.0.0.251. This is a
On Sat, 14.10.06 15:59, Joey Hess ([EMAIL PROTECTED]) wrote:
Seems my last mail crossed yours on the way.
> Part of the problem is that your /etc/resolv.conf has "search local".
> This means that every dns lookup is first tried in the "local" domain,
> so it's trying to look up google.com.local.
First, to answer your questions:
- ping is netkit-ping 0.10-10.3.
- a full strace of the failing ping (as root) is below
My own theory:
- It is not a problem with ping, other programs fail as well.
- It fails after trying to send to 224.0.0.251. This is a multicast
address. My name server is
It would be helpful to know what version of ping you have, from which
package. Based on the strace, it doesn't look like the ping from
iputils-ping 3:20020927-3 or the one from netkit-ping 0.10-10.3. For one
thing, it reads from /dev/urandom, which neither of those seem to do.
It also seems that
6 matches
Mail list logo
