This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/395] resolver updates causes resolver to stop resolving some hosts
- From: "vapier at gentoo dot org" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 28 Sep 2004 03:56:20 -0000
- Subject: [Bug libc/395] resolver updates causes resolver to stop resolving some hosts
- References: <20040921043809.395.vapier@gentoo.org>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From vapier at gentoo dot org 2004-09-28 03:56 -------
'options ndots:0' restored the previous behavior like i described and like you said
i'm not sure if there are any specs which cover the 'proper' behavior with
respect to resolv.conf/domain/etc... (SuSv3 and such) but like you say, when
using the 'domain' option in resolv.conf, this seems like 'proper' behavior,
even it does take 'more' effort to get back to the older/simpler behavior
perhaps we can get the man page to make a note of the 'expected' behavior under
the ndots section so that people (such as myself) wont file anymore 'invalid'
bugs unknowingly ?
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=395
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.