Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When my CentOS virtual machine boots it uses DHCP to get an IP address. It also overwrites resolv.conf with the DNS settings provided by the DHCP server. The DHCP server doesn't supply any search domains so I would like to get dhclient to put in a list of search domains when it writes it. How can I configure dhclient to do this?

share|improve this question

10 Answers 10

None of those worked, but the last one was the closest. For Red Hat 6, Use DOMAIN instead of SEARCH as in the example above and the file location is different.

I modified the file /etc/sysconfig/network-scripts/ifcfg-eth0

and changed



and it all worked.

share|improve this answer
You should be able to use both DOMAIN and SEARCH – Radek Simko Jan 14 '14 at 21:49
This technique of setting DOMAIN also worked for me on CentOS 6.5, even though my resolve.conf is generated by NetworkManager rather than dhclient. The generated resolve.conf file combined my entries with those from the DHCP server. – PolyTekPatrick Aug 13 '15 at 2:51

Also you can add string to /etc/dhcp3/dhclient.conf like this

prepend domain-search "", "";

Note, that this method works with Debian Lenny and Squeeze, too.

share|improve this answer

I managed to work this out in the end. I added a line like the following to /etc/dhclient-eth0.conf

append domain-name "";
share|improve this answer

On CentOS 6, I'm using the following file to add my preferred DNS search domain:

[root@beamish ~]# cat /etc/dhcp/dhclient-eth0.conf 
interface "eth0" {
    supersede domain-search "";
[root@beamish ~]# getenforce 
[root@beamish ~]# ls -lZ /etc/dhcp/dhclient-eth0.conf 
-rw-r--r--. root root system_u:object_r:bin_t:s0   /etc/dhcp/dhclient-eth0.conf
[root@beamish ~]#

This file is the first that's checked for in /etc/sysconfig/network-scripts/ifup-eth:

if [ -s /etc/dhcp/dhclient-${DEVICE}.conf ]; then
   DHCLIENTCONF="-cf /etc/dhcp/dhclient-${DEVICE}.conf";

See also

share|improve this answer
One note to add - if you're specifying multiple search domains to dhclient by using (option|supersede|*) domain-search ..., make sure you follow the dhcp-options(5) man page spec for quoting individual domains: option domain-search "", "", ""; Many older distributions of dhclient allowed the format ""; but this compatibility has been removed in the past few years due to bug fixes – Patrick Apr 11 '13 at 4:42

The /etc/dhclient-eth0.conf answer above didn't work for me. I don't have an /etc/dhcp3 directory so I didn't think that was likely to work either.

After examining the /sbin/dhclient-script file (which creates /etc/resolv.conf on my Centos 5.6 system), I added the SEARCH line below to /etc/sysconfig/networking/devices/ifcfg-eth0:



# ifdown eth0
# ifup eth0
#  cat /etc/resolv.conf
; generated by /sbin/dhclient-script
share|improve this answer

For anyone going through Fedora / Red Hat's rather opaque pile of scripts, the answer, at least on Amazon's latest AMI, it is /etc/dhclient-eth0.conf (and not the decoy empty folder at /etc/dhcp/ ). The file is not present and will need to be created

share|improve this answer
Adding SEARCH to ifcfg-eth0/etc/sysconfig/network-scripts/ifcfg-eth0 also works on the Amazon version of Fedora. In older versions of Red Hat it apparently was DOMAIN. I wpould recommend this over the above. – Dr David C Crooke Sep 20 '13 at 20:20

In Fedora 19 add next lines to /etc/dhcp/dhclient.conf

# /etc/dhcp/dhclient.conf

interface "p2p1"
    supersede domain-name-servers,;
    append domain-name "";

Work fine with NetworkManager. Details see: # man dhclient.conf

share|improve this answer

This is mostly a note for RHEL7 to reduce trial and error. Dean's answer of using DOMAIN="" in /etc/sysconfig/network-scripts/ifcfg-device.conf works. An interesting note is the host's domain that the connection gets from DHCP is always prepended to the search path, even if you leave it out of DOMAIN= or put it later in a list for DOMAIN=. It looks like /sbin/dhclient-script has a bunch of logic in there related to this.

In my testing, I found that Philip's suggestion of using /etc/dhcp/dhclient-device.conf also works, although there is some strange behavior with that, most likely due to that same logic in /sbin/dhclient-script that tries to move things around. For instance, neither supercede or prepend work as expected, the host's domain will be first. As a side note on this method, /var/lib/NetworkManager/dhclient-device.conf is the generated NetworkManager file and is used by the client. If you have a file in /etc/dhcp/ that gets read in, you'll see it pasted at the top of the file and a few extra options added below.

share|improve this answer

Add to the dchp server conf (isc dhcpd):

option domain-name "";

Where,etc.. are the domain suffixes you want added to the resolv.conf file on each client.

share|improve this answer

Since I don't see this answer and it worked for me (while the others didn't), here it is: edit /etc/resolvconf/resolv.conf.d/base the same way as you would /etc/resolv.conf. You'll need resolvconf installed.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .