/etc/resolv.conf

Comments

• iKocka Member

  October 2011

  Do you have DHCP enabled?
• rds100 Member

  October 2011

  option one - chattr +i /etc/resolv.conf (not sure if it will work, maybe try it)
  
  Option two - modify/overwrite resolv.conf with your own version from rc.local for instance. But the all daemons that start before rc.local runs would use the hosts's resolv.conf
• biplab Member

  October 2011

  Set PEERDNS=no in ifcfg-venet0 file.
• ztec Member

  October 2011

  Just don't reboot :P
• Kuro Member

  October 2011

  I think OpenVZ overwrites the resolv.conf file when it boots the VPS.
• gsrdgrdghd Member

  October 2011

  Make a script that overwrites the overwritten file on startup
• Intcs Member

  October 2011

  gsrdgrdghd said: Make a script that overwrites the overwritten file on startup

  At times this solution works.
• cripperz Member

  October 2011

  your /etc/resolv.conf is being written by solusvm-openvz script on startup generally when the host provider sets its block of IP to a specific dns ip. Maybe easiest way is for you to just create a startup script or a crontab entry and insert the echo commands below

  echo "nameserver 127.0.0.1" >> /etc/resolv.conf
• Spirit Barred

  October 2011 edited October 2011

  nano /etc/rc.local
  
  echo 'nameserver 4.8.8.8' > /etc/resolv.conf

  or

  nano /etc/rc.local
  
  cp /backup/resolv.conf /etc/resolv.conf
  
  

  Or:

  cripperz said: Maybe easiest way is for you to just create a startup script

  
  ..and use @reboot crontab command (it will execute your script only after reboot)

  export EDITOR=nano
  
  crontab -e
  
  @reboot cd /root; ./resolv.sh >/dev/null 2>&1