{"id":4382,"date":"2022-12-20T17:49:07","date_gmt":"2022-12-20T20:49:07","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/host-conf-man5\/"},"modified":"2022-12-20T17:49:07","modified_gmt":"2022-12-20T20:49:07","slug":"host-conf-man5","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/host-conf-man5\/","title":{"rendered":"HOST.CONF (man5)"},"content":{"rendered":"

HOST.CONF<\/h1>\n

NAME<\/a>
DESCRIPTION<\/a>
ENVIRONMENT<\/a>
FILES<\/a>
NOTES<\/a>
SEE ALSO<\/a>
COLOPHON<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

host.conf \u2212 resolver configuration file<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

The file \/etc\/host.conf<\/i> contains configuration information specific to the resolver library. It should contain one configuration keyword per line, followed by appropriate configuration information. The following keywords are recognized:<\/p>\n\n\n\n
<\/td>\n\n

trim<\/i><\/p>\n<\/td>\n

<\/td>\n\n

This keyword may be listed more than once. Each time it should be followed by a list of domains, separated by colons (‘:’), semicolons (‘;’) or commas (‘,’), with the leading dot. When set, the resolver library will automatically trim the given domain name from the end of any hostname resolved via DNS. This is intended for use with local hosts and domains. (Related note: trim<\/i> will not affect hostnames gathered via NIS or the hosts<\/b>(5) file. Care should be taken to ensure that the first hostname for each entry in the hosts file is fully qualified or unqualified, as appropriate for the local installation.)<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

multi<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Valid values are on<\/i> and off<\/i>. If set to on<\/i>, the resolver library will return all valid addresses for a host that appears in the \/etc\/hosts<\/i> file, instead of only the first. This is off<\/i> by default, as it may cause a substantial performance loss at sites with large hosts files.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

reorder<\/i><\/p>\n

Valid values are on<\/i> and off<\/i>. If set to on<\/i>, the resolver library will attempt to reorder host addresses so that local addresses (i.e., on the same subnet) are listed first when a gethostbyname<\/b>(3) is performed. Reordering is done for all lookup methods. The default value is off<\/i>.<\/p>\n

ENVIRONMENT <\/a> <\/h2>\n

The following environment variables can be used to allow users to override the behavior which is configured in \/etc\/host.conf<\/i>:
RESOLV_HOST_CONF<\/b><\/p>\n

If set, this variable points to a file that should be read instead of \/etc\/host.conf<\/i>.<\/p>\n

RESOLV_MULTI<\/b><\/p>\n

Overrides the multi<\/i> command.<\/p>\n

RESOLV_REORDER<\/b><\/p>\n

Overrides the reorder<\/i> command.<\/p>\n

RESOLV_ADD_TRIM_DOMAINS<\/b><\/p>\n

A list of domains, separated by colons (‘:’), semicolons (‘;’) or commas (‘,’), with the leading dot, which will be added to the list of domains that should be trimmed.<\/p>\n

RESOLV_OVERRIDE_TRIM_DOMAINS<\/b><\/p>\n

A list of domains, separated by colons (‘:’), semicolons (‘;’) or commas (‘,’), with the leading dot, which will replace the list of domains that should be trimmed. Overrides the trim<\/i> command.<\/p>\n

FILES <\/a> <\/h2>\n

\/etc\/host.conf<\/i><\/p>\n

Resolver configuration file<\/p>\n

\/etc\/resolv.conf<\/i><\/p>\n

Resolver configuration file<\/p>\n

\/etc\/hosts<\/i><\/p>\n

Local hosts database<\/p>\n

NOTES <\/a> <\/h2>\n

The following differences exist compared to the original implementation. A new command spoof<\/i> and a new environment variable RESOLV_SPOOF_CHECK<\/b> can take arguments like off<\/i>, nowarn<\/i>, and warn<\/i>. Line comments can appear anywhere and not only at the beginning of a line.<\/p>\n

Historical<\/b>
The nsswitch.conf<\/b>(5) file is the modern way of controlling the order of host lookups.<\/p>\n

In glibc 2.4 and earlier, the following keyword is recognized:<\/p>\n\n\n
<\/td>\n\n

order<\/i><\/p>\n<\/td>\n

<\/td>\n\n

This keyword specifies how host lookups are to be performed. It should be followed by one or more lookup methods, separated by commas. Valid methods are bind<\/i>, hosts<\/i>, and nis<\/i>.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

RESOLV_SERV_ORDER<\/b><\/p>\n

Overrides the order<\/i> command.<\/p>\n

Since glibc 2.0.7, and up through glibc 2.24, the following keywords and environment variable have been recognized but never implemented:
nospoof<\/i><\/p>\n

Valid values are on<\/i> and off<\/i>. If set to on<\/i>, the resolver library will attempt to prevent hostname spoofing to enhance the security of rlogin<\/b> and rsh<\/b>. It works as follows: after performing a host address lookup, the resolver library will perform a hostname lookup for that address. If the two hostnames do not match, the query fails. The default value is off<\/i>.<\/p>\n

spoofalert<\/i><\/p>\n

Valid values are on<\/i> and off<\/i>. If this option is set to on<\/i> and the nospoof<\/i> option is also set, the resolver library will log a warning of the error via the syslog facility. The default value is off<\/i>.<\/p>\n\n\n
<\/td>\n\n

spoof<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Valid values are off<\/i>, nowarn<\/i>, and warn<\/i>. If this option is set to off<\/i>, spoofed addresses are permitted and no warnings will be emitted via the syslog facility. If this option is set to warn<\/i>, the resolver library will attempt to prevent hostname spoofing to enhance the security and log a warning of the error via the syslog facility. If this option is set to nowarn<\/i>, the resolver library will attempt to prevent hostname spoofing to enhance the security but not emit warnings via the syslog facility. Setting this option to anything else is equal to setting it to nowarn<\/i>.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

RESOLV_SPOOF_CHECK<\/b><\/p>\n

Overrides the nospoof<\/i>, spoofalert<\/i>, and spoof<\/i> commands in the same way as the spoof<\/i> command is parsed. Valid values are off<\/i>, nowarn<\/i>, and warn<\/i>.<\/p>\n

SEE ALSO <\/a> <\/h2>\n

gethostbyname<\/b>(3), hosts<\/b>(5), nsswitch.conf<\/b>(5), resolv.conf<\/b>(5), hostname<\/b>(7), named<\/b>(8)<\/p>\n

COLOPHON <\/a> <\/h2>\n

This page is part of release 5.10 of the Linux man-pages<\/i> project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https:\/\/www.kernel.org\/doc\/man\u2212pages\/.<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

host.conf \u2212 resolver configuration file <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[959],"tags":[961,1389,1291],"class_list":["post-4382","post","type-post","status-publish","format-standard","hentry","category-5-formatos-de-ficheros","tag-961","tag-host","tag-man5"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4382","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4382"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4382\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4382"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4382"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4382"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}