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
what happens if you set 'options ndots:0' in /etc/resolv.conf ?
<feeling-stupid>Yes, that works now, thanks.</feeling-stupid>
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 :(
