Package: libadns1 Version: 1.4-0.1 Severity: normal
a cname chain is a cname pointint to another cname alias instead of to the canonical name, as it should. libadns doesn't support this and fails to resolve. while there is no clear standard on this (the dns rfcs are a mess), libadns's interpretation is not "wrong" or "non-standard" w.r.t. the rfcs. however, consider changing this into supporting cname chains, as: - use of cname chains is widespread (libadns cannot resolve www.google.de for example, a real showstopper for e.g. a web browser or http library). - support for cname chains is almost universal in other dns resolvers (libadns is the exception in not supporting them). this bug and failure to support multiple ptr records keeps libadns from being generally usable. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libadns1 depends on: hi libc6 2.7-10 GNU C Library: Shared libraries Versions of packages libadns1 recommends: ii libadns1-bin 1.4-0.1 Asynchronous-capable DNS client li -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
