/etc/resolv.conf: Difference between revisions
| (13 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
* [[Bind_Operations_-_Set_Up_DNS_Client#.2Fetc.2Fresolv.conf|Setup a DNS client]] | * [[Bind_Operations_-_Set_Up_DNS_Client#.2Fetc.2Fresolv.conf|Setup a DNS client]] | ||
* [[Linux_7_Configuring_a_Network_Interface#PEERDNS|PEERDNS]] | |||
* [[/etc/nsswitch.conf|/etc/nsswitch.conf]] | |||
=Overview= | =Overview= | ||
| Line 13: | Line 15: | ||
=Who Writes It?= | =Who Writes It?= | ||
Network configuration scripts or [[NetworkManager]] write <tt>/etc/resolv.conf</tt> when configured to do so (see PEERDNS=yes), | Network configuration scripts like /usr/sbin/dhclient-script or [[NetworkManager]] write <tt>/etc/resolv.conf</tt> when configured to do so (see [[Linux_7_Configuring_a_Network_Interface#PEERDNS|PEERDNS]]=yes). | ||
If PEERDNS is set to "no", you will need to edit it manually. | |||
=Configure DNS via /etc/sysconfig/network-scripts= | =Configure DNS via /etc/sysconfig/network-scripts= | ||
The following settings should be specified in | The following settings should be specified in /etc/sysconfig/network-scripts/ifcfg-ethX: | ||
To configure the DNS resolver with a specific DNS server and '''NOT''' the DNS server that comes with DHCP configuration, set: | To configure the DNS resolver with a specific DNS server and '''NOT''' the DNS server that comes with DHCP configuration, set: | ||
| Line 23: | Line 27: | ||
<pre> | <pre> | ||
NM_CONTROLLED=no | NM_CONTROLLED=no | ||
PEERDNS=no | PEERDNS=no | ||
IPV6_PEERDNS=no | IPV6_PEERDNS=no | ||
| Line 39: | Line 42: | ||
<font color=red>The network configuration scripts will write this into /etc/resolv.conf. Actually, if I set PEERDNS=no, nothing is written, I need to write it manually. Return to this.</font> | <font color=red>The network configuration scripts will write this into /etc/resolv.conf. Actually, if I set PEERDNS=no, nothing is written, I need to write it manually. Return to this.</font> | ||
Also see [[ | Also see [[NetworkManager_Operations#Disable_the_Network_Manager|Disable the NetworkManager - NM_CONTROLLED]]. | ||
= | <span id="Manual_resolv.conf_Configuration"></span>Alternatively, NetworkManager can be configured to NOT touch /etc/resolv.conf. The configuration is described here: {{Internal|NetworkManager_Configuration#.2Fetc.2Fresolv.conf_Processing_Mode|Configuring NetworkManager not to modify /etc/resolv.conf}} | ||
In both cases, /etc/resolv.conf must be manually updated as follows: | |||
<pre> | <pre> | ||
| Line 99: | Line 91: | ||
==Search== | ==Search== | ||
<code>search</code> contains the search list of host name lookup. Its elements represent strings added to non-canonical host names when those non-canonical host names are resolved to IP addresses. | |||
The search list is normally determined from the local domain name, and by default it contains only the local domain name. | The search list is normally determined from the local domain name, and by default it contains only the local domain name. | ||
This may be changed by listing the desired domain search path following the < | This may be changed by listing the desired domain search path following the <code>search</code> keyword. It is used as follows: resolver queries having fewer than 1 dot will be attempted using each component of the search path in turn until a match is found. | ||
< | <syntaxhighlight lang='text'> | ||
search novaordis.com | search novaordis.com | ||
</ | </syntaxhighlight> | ||
Latest revision as of 01:12, 22 November 2021
External
Internal
Overview
/etc/resolv.conf is the name of the file that configures the DNS resolver. The DNS resolver is a set of routines in the C library that provide access to DNS. Among other things, /etc/resolv.conf configures the default search domains and the nameserver IP addresses.
Who Writes It?
Network configuration scripts like /usr/sbin/dhclient-script or NetworkManager write /etc/resolv.conf when configured to do so (see PEERDNS=yes).
If PEERDNS is set to "no", you will need to edit it manually.
Configure DNS via /etc/sysconfig/network-scripts
The following settings should be specified in /etc/sysconfig/network-scripts/ifcfg-ethX:
To configure the DNS resolver with a specific DNS server and NOT the DNS server that comes with DHCP configuration, set:
NM_CONTROLLED=no PEERDNS=no IPV6_PEERDNS=no
Note that setting only one is not sufficient, both need to be set.
Then specify the DNS IP address with:
DNS1="8.8.8.8" DNS2="8.8.4.4"
The network configuration scripts will write this into /etc/resolv.conf. Actually, if I set PEERDNS=no, nothing is written, I need to write it manually. Return to this.
Also see Disable the NetworkManager - NM_CONTROLLED.
Alternatively, NetworkManager can be configured to NOT touch /etc/resolv.conf. The configuration is described here:
In both cases, /etc/resolv.conf must be manually updated as follows:
# Manual 09/21/15 domain openshift.local search openshift.local nameserver 172.20.2.10
Content
/etc/resolv.conf contains:
Nameservers
The nameserver is the DNS server IPv4 or IPv6 address.
Up to MAXNS (currently 3, specified in resolv.h) name servers may be listed, one per keyword.
If multiple servers are listed, they are queried in order.
If no name server is specified, the default is to use the name server on the local machine.
Example:
nameserver 206.13.28.12 nameserver 206.13.28.13 nameserver 206.13.28.14
Domain
The domain keyword specifies the local domain name.
If no domain entry is present, the domain is determined from the local hostname returned by gethostname by taking everything after the first ".". If the hostname does not contain a domain part, the root domain is assumed.
Example:
domain openshift.local
Search
search contains the search list of host name lookup. Its elements represent strings added to non-canonical host names when those non-canonical host names are resolved to IP addresses.
The search list is normally determined from the local domain name, and by default it contains only the local domain name.
This may be changed by listing the desired domain search path following the search keyword. It is used as follows: resolver queries having fewer than 1 dot will be attempted using each component of the search path in turn until a match is found.
search novaordis.com