+++ This bug was initially created as a clone of Bug #703239 +++

Description of problem:

If /etc/resolv.conf contains an IPv6 nameserver entry with a space after the IP address, then clients only try to resolve the entry via the localhost, which fails because I don't have a nameserver locally:
# cat -e /etc/resolv.conf
nameserver 2001:470:20::2 $
# ping6 ipv6.google.com
unknown host
# strace -e connect ping6 ipv6.google.com
connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"...}, 110) = -1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"...}, 110) = -1 ENOENT (No such file or directory)
connect(4, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("0.0.0.0")}, 28) = 0
connect(4, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("0.0.0.0")}, 28) = 0
connect(4, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("0.0.0.0")}, 28) = 0
connect(4, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("0.0.0.0")}, 28) = 0
unknown host
# 

I'd guess the extra white space causes the resolver to treat the entry as a hostname or some other invalid entry.

This caused me some confusion until I worked out I had an extra space at the end of the line, because the "dig" and "host" tools were working correctly (they don't use the glibc resolver).

Version-Release number of selected component (if applicable):
Seen in RHEL5.1 and RHEL5.4

How reproducible:
Always

Steps to Reproduce:
1. Enter a whitespace after the IPv6 address.
2. Try to ping6 a hostname
3.
  
Actual results:
"unknown host" and ping6 returns exit code 2.

Expected results:
Normal ping output.

Additional info: