Difference between revisions of "Resolv.conf"

From ArchWiki
Jump to: navigation, search
(link to man page too)
(Preserve DNS settings: made some paths to /etc/resolv.conf include the full path)
Line 7: Line 7:
  
 
==Preserve DNS settings==
 
==Preserve DNS settings==
Dhcpcd, [[NetworkManager]], and various other processes can overwrite {{Filename|/etc/resolv.conf}}. This is usually desirable behavior, but sometimes DNS settings need to be set manually (e.g. when using a static IP). There are several ways to accomplish this. If you are using NetworkManager, see [http://bbs.archlinux.org/viewtopic.php?id=45394 this thread] on how to prevent it from overriding your {{Filename|resolv.conf}}.
+
{{Pkg|dhcpcd}}, [[NetworkManager]], and various other processes can overwrite {{Filename|/etc/resolv.conf}}. This is usually desirable behavior, but sometimes DNS settings need to be set manually (e.g. when using a static IP address). There are several ways to accomplish this. If you are using NetworkManager, see [http://bbs.archlinux.org/viewtopic.php?id=45394 this thread] on how to prevent it from overriding your {{Filename|/etc/resolv.conf}}.
  
 
===Modify the dhcpcd Config===
 
===Modify the dhcpcd Config===
Dhcpcd's configuration file may be edited to prevent the dhcpcd daemon from overwriting {{Filename|/etc/resolv.conf}}. To do this, add the following to the last section of {{Filename|/etc/dhcpcd.conf}}:  
+
dhcpcd's configuration file may be edited to prevent the dhcpcd daemon from overwriting {{Filename|/etc/resolv.conf}}. To do this, add the following to the last section of {{Filename|/etc/dhcpcd.conf}}:  
  
 
  nohook resolv.conf
 
  nohook resolv.conf
  
 
===Use resolv.conf.head===
 
===Use resolv.conf.head===
Alternatively, you can create a file called {{Filename|/etc/resolv.conf.head}} containing your DNS servers. Dhcpcd will prepend this file to the beginning of {{Filename|resolv.conf}}. An example {{Filename|/etc/resolv.conf.head}} for someone using [[OpenDNS]] would be:
+
Alternatively, you can create a file called {{Filename|/etc/resolv.conf.head}} containing your DNS servers. dhcpcd will prepend this file to the beginning of {{Filename|/etc/resolv.conf}}. An example {{Filename|/etc/resolv.conf.head}} for someone using [[OpenDNS]] would be:
  
 
  # OpenDNS servers
 
  # OpenDNS servers
Line 21: Line 21:
 
  nameserver 208.67.220.220
 
  nameserver 208.67.220.220
  
If you are not pleased with the OpenDNS servers you might try [http://code.google.com/speed/public-dns/ Google's nameservers] as an alternative.
+
If you are not pleased with the OpenDNS servers, you might try [http://code.google.com/speed/public-dns/ Google's nameservers] as an alternative.
  # google nameservers
+
  # Google nameservers
 
  nameserver 8.8.8.8
 
  nameserver 8.8.8.8
 
  nameserver 8.8.4.4
 
  nameserver 8.8.4.4
  
===Write-protect resolv.conf===
+
===Write-protect /etc/resolv.conf===
Another way to protect your {{filename|resolv.conf}} from being modified by anything is setting the write-protection attribute:
+
Another way to protect your {{Filename|/etc/resolv.conf}} from being modified by anything is setting the write-protection attribute:
 
  chattr +i /etc/resolv.conf
 
  chattr +i /etc/resolv.conf
  
 
===Use timeout option to reduce hostname lookup time===
 
===Use timeout option to reduce hostname lookup time===
If you are confronted with a very long hostname lookup (may it be in pacman or while browsing) it often helps to define a small timeout after which an alternative nameserver is used. To do so create a file called {{Filename|/etc/resolv.conf.tail}} and add the following line:
+
If you are confronted with a very long hostname lookup (may it be in [[pacman]] or while browsing), it often helps to define a small timeout after which an alternative nameserver is used. To do so, create a file called {{Filename|/etc/resolv.conf.tail}} and add the following line:
 
  options timeout:1
 
  options timeout:1
  
 
Then restart your network daemon and see if it works better.
 
Then restart your network daemon and see if it works better.

Revision as of 18:07, 31 October 2011

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

From from the resolv.conf(5) man page:

"The resolver is a set of routines in the C library that provide access to the Internet Domain Name System (DNS). The resolver configuration file contains information that is read by the resolver routines the first time they are invoked by a process. The file is designed to be human readable and contains a list of keywords with values that provide various types of resolver information.
"On a normally configured system this file should not be necessary. The only name server to be queried will be on the local machine; the domain name is determined from the host name and the domain search path is constructed from the domain name."

Preserve DNS settings

dhcpcd, NetworkManager, and various other processes can overwrite Template:Filename. This is usually desirable behavior, but sometimes DNS settings need to be set manually (e.g. when using a static IP address). There are several ways to accomplish this. If you are using NetworkManager, see this thread on how to prevent it from overriding your Template:Filename.

Modify the dhcpcd Config

dhcpcd's configuration file may be edited to prevent the dhcpcd daemon from overwriting Template:Filename. To do this, add the following to the last section of Template:Filename:

nohook resolv.conf

Use resolv.conf.head

Alternatively, you can create a file called Template:Filename containing your DNS servers. dhcpcd will prepend this file to the beginning of Template:Filename. An example Template:Filename for someone using OpenDNS would be:

# OpenDNS servers
nameserver 208.67.222.222
nameserver 208.67.220.220

If you are not pleased with the OpenDNS servers, you might try Google's nameservers as an alternative.

# Google nameservers
nameserver 8.8.8.8
nameserver 8.8.4.4

Write-protect /etc/resolv.conf

Another way to protect your Template:Filename from being modified by anything is setting the write-protection attribute:

chattr +i /etc/resolv.conf

Use timeout option to reduce hostname lookup time

If you are confronted with a very long hostname lookup (may it be in pacman or while browsing), it often helps to define a small timeout after which an alternative nameserver is used. To do so, create a file called Template:Filename and add the following line:

options timeout:1

Then restart your network daemon and see if it works better.