Re: DNS Resolution and Short Names with Dots

2014-09-26 Thread Pascal Hambourg
Mark Kamichoff a écrit : If the change is in libc, it appears to be between 2.19-4 and 2.19-7. http://metadata.ftp-master.debian.org/changelogs//main/g/glibc/glibc_2.19-11_changelog .. doesn't seem to indicate any resolver / DNS changes between those versions, though. I'll continue to

Re: DNS Resolution and Short Names with Dots

2014-09-26 Thread Mark Kamichoff
On Fri, Sep 26, 2014 at 04:56:17PM +0200, Pascal Hambourg wrote: Interstingly, libc6 switched back from eglibc to glibc sources just before 2.19-4. The uptime on most of my systems is pretty high and it's possible that through various dist-upgrades I've gone between eglibc and glibc without

Re: DNS Resolution and Short Names with Dots

2014-09-25 Thread Mark Kamichoff
On Wed, Sep 24, 2014 at 11:30:43AM -0400, Mark Kamichoff wrote: On Wed, Sep 24, 2014 at 08:55:51AM +0100, Karl E. Jorgensen wrote: Perhaps one of the recent libc upgrades have changed the default for 'ndots' ? If so, according to a quick scan of the resolv.conf(5) manual page you

Re: DNS Resolution and Short Names with Dots

2014-09-24 Thread Karl E. Jorgensen
Hi On Tue, Sep 23, 2014 at 05:46:29PM -0400, Mark Kamichoff wrote: Hi - I've been running into somewhat inconsistent behavior with DNS short name resolution in Debian across a few systems. Here's the behavior that I've occasionally relied on over the years: % cat /etc/resolv.conf

Re: DNS Resolution and Short Names with Dots

2014-09-24 Thread Mark Kamichoff
On Wed, Sep 24, 2014 at 08:55:51AM +0100, Karl E. Jorgensen wrote: Perhaps one of the recent libc upgrades have changed the default for 'ndots' ? If so, according to a quick scan of the resolv.conf(5) manual page you should be able add this to /etc/resolv.conf to get your old behaviour

DNS Resolution and Short Names with Dots

2014-09-23 Thread Mark Kamichoff
Hi - I've been running into somewhat inconsistent behavior with DNS short name resolution in Debian across a few systems. Here's the behavior that I've occasionally relied on over the years: % cat /etc/resolv.conf search example.com nameserver 192.0.2.10 % host foo.bar.baz.example.com.