• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 207
  • Last Modified:

Can't get /etc/resolv.conf to configure after reboot

This is a redhat Linux server 6.3.
when I reboot the resolv.conf file has no dns servers listed.

I have a number of VLANs attached to a single interface.  they are set up as ifcfg-eth0:1 through 6
According to the docs I've read the interface config should look something like this:
DEVICE="eth0"
BOOTPROTO="static"
NM_CONTROLLED="no"
ONBOOT=yes
TYPE="Ethernet"
UUID="81eaafdb-2746-4566-a556-06c2c2ada461"
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
HWADDR=AC:16:2D:74:05:D4
PEERDNS=yes
RESOLV_MODS=no
PEERROUTES=no
IPADDR=xx.26.154.35
GATEWAY=xx.26.154.33
NETMASK=255.255.255.224
DNS1=206.191.0.140
DNS2=206.191.0.210
DOMAIN=xxxnet.ca

It states that in order for resolv.conf to be set up your have to have PEERDNS set to yes and DNS1 and DNS2 set up in the config file.
which I have done.

In the VLAN files I have tried setting PEERDNS to no for all of them and then to yes for all of them. But it still doesn't set up resolv.conf properly.

If looked at the ifup_post script and it looks like it should have done something but I haven't tried debugging them.  I'm working remotely so if I mess up the network scripts, I might not be able to get on.

in the resolv.conf part of the ifup_post script it creates a backup copy of the resolv.conf file.  That backup copy does exist in /etc so that leads me to suspect it's running through the right part of the script.  The really weird thing is, the backup copy has two lines in it for name servers that are not the ones that I use.  They come from an alternate datacenter that we use for other applications.
I've grepped all the files in /etc to see if the ip address exists in any of the files, but nothing showed up.

Not sure what to do next.
0
geekdad1
Asked:
geekdad1
  • 3
  • 3
1 Solution
 
gheistCommented:
Option 1 You can disable PEERDNS and use reolv.conf with 2 DNS servers
Option 2 you can add or replace DHCP DNS servers via dhclient.conf or equivalent

You must upgrade your system, with most expensive support option it is 2 years overdue:
In Red Hat Enterprise Linux 6, EUS is available for the following minor releases:
6.3 (ends June 30, 2014)
Alternatively you can upgrade to CentOS or Oracle linux for free.
0
 
geekdad1Author Commented:
Setting PEERDNS to no on all interfaces doesn't make any difference.
DHCP is not an option . This host has a static IP address.

We are aware of the age of the server and are looking at our options.  Free is not always the best consideration.
0
 
gheistCommented:
Just remove DNS settings from /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-eth0 and customize resolv.conf to your liking (I think DNS in first file overrides 2nd)
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
amishra1Commented:
You can enter your desired dns in /etc/resolvconf/resolv.conf.d/head file. This will make sure when server is rebooted, DNS entries from head file are applied in /etc/resolve.conf

Let me know if that helps.
0
 
geekdad1Author Commented:
No such animal on my system.  However I think since we have virtual ip's running that PEERDNS flag needs to be set to no for all of them except the very first (non virtual) device.  I can't reboot the server just now but I will post again once I get a chance to.
0
 
gheistCommented:
If you want fixed named.conf just make sure NetworkManager does not overwrite it?
resolvconf is debian stuff, you can skip that part ;)
0
 
geekdad1Author Commented:
Takes a long time to test these things since I can't take the server down except for exceptional circumstances.  Will be moving to a new server soon, so this problem should resolv itself.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now