Bug 87192

Summary:	glibc-2.3.4.20041102-r1 has broken name resolution for "."
Product:	Gentoo Linux	Reporter:	James Roberts-Thomson <james.roberts-thomson>
Component:	[OLD] Core system	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED INVALID
Severity:	major
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description James Roberts-Thomson 2005-03-29 17:38:01 UTC

I use Gentoo at my workplace, where we have our own internal DNS system.  For historic reasons, our internal DNS defines our own "." domain, and many machines are entered into it.

Prior to my glibc upgrade, my machine could resolve to machines in our internal "." domain, so "ping machine" where the FQDN was actually "machine." worked.

With glibc-20041102, it doesn't.  Nothing has changed with respect to nsswitch.conf, resolv.conf etc.  Reverting back to glibc-20040808 brings back the old behaviour.

nsswitch.conf can resolve the machines OK; but other tools (like ping, ssh, etc) no longer can automatically - makes system administration difficult.  Using FQDNs work, i.e. "ping machine.", but a large number of scripts and other settings mean I'd rather this wasn't the permanent solution.

I know we shouldn't be using the "." domain internally, but this is beyond my power to change.

Is there any known workaround?


Reproducible: Always
Steps to Reproduce:
1.  emerge glibc-2.3.4-20041102
2.  Notice that things like "ping machine" no longer work correctly.

Actual Results:  
ping: unknown host

Comment 1 SpanKY gentoo-dev

2005-03-30 14:53:48 UTC

what happens if you set 'options ndots:0' in /etc/resolv.conf ?

Comment 2 James Roberts-Thomson 2005-03-30 14:58:29 UTC

<feeling-stupid>Yes, that works now, thanks.</feeling-stupid>

Comment 3 SpanKY gentoo-dev

2005-03-30 15:00:19 UTC

nah, it's a change in behavior that caught me off gaurd too ... i filed a bug upstream and i was told that this was an intended change :(