I don't believe it is correct to say unused. Host.conf is still parsed and
various directives obeyed. An absent / empty file may well be a sane default,
but glibc still reads the file - just strace any process doing a name lookup.
Fwiw fedora 18 has:
multi on
...in the file.
the host.conf
DNS
before it starts up (you simply have to edit the config files in /etc/systemd
Subject: Re: Unwanted resolver usage of /etc/host.conf
From: bryanlhar...@me.com
Date: Sat, 23 Feb 2013 16:07:58 -0500
To: and...@hpl.hp.com
CC: bind-us...@isc.org
On Feb 22, 2013, at 10:28 PM
On Feb 22, 2013, at 10:28 PM, Andris Kalnozols and...@hpl.hp.com wrote:
I stumbled upon the /etc/host.conf file and had to add the following
line to get name resolution working again:
order hosts,bind
On 23.02.13 16:07, Bryan Harris wrote:
I thought Linux should have that line by default.
On Feb 22, 2013, at 10:28 PM, Andris Kalnozols and...@hpl.hp.com wrote:
I stumbled upon the /etc/host.conf file and had to add the following
line to get name resolution working again:
order hosts,bind
I thought Linux should have that line by default. Do you think someone has
removed that
Hi.
Although not a BIND-related issue, I would like to ask if someone could
explain the conditions under which a compiled C program on Linux could
be made to have a name resolution dependency on the settings within the
file `/etc/host.conf'. As I understand things, host.conf is the ancestor
of
5 matches
Mail list logo
