[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#420301: marked as done (libc6: IPv6 transport fails for resolver)

Your message dated Sun, 22 Apr 2007 15:27:21 +0200
with message-id <87tzv8sfnq.fsf@mid.deneb.enyo.de>
and subject line Bug#420301: libc6: IPv6 transport fails for resolver
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: libc6
Version: 2.5-2
Severity: normal


When I specify an IPv6 address as my nameserver, resolution fails instantly and
a packet trace reveals no traffic.  For instance if I specify only:

nameserver 2002:CFAC:5504:2::0

in /etc/resolv.conf, no queries go out.  Not sure if this is a glibc 
compile-time option to disable this feature, but I'm pretty sure that glibc has 
supported IPv6 transport on resolution since version 2.2.  Using the dig command 
directly (with the -6 option) of course allows me to use IPv6 as transport, so I 
know v6 routing and other config is set up right.

I have tried this with both 'options inet6' on and off.  Let me know if I can
provide any more information.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.20
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

-- no debconf information

--- End Message ---
--- Begin Message ---
* Tim:

> Thanks for the tip, I should have thought of it.  I just realized my
> problem... the 'host' package does not support IPv6 transport.  After
> fully debugging the issue with other tools, I found that things are
> working fine.  Please close this bug, sorry for the trouble.

Closing, as requested.

--- End Message ---

Reply to: