The dns servers on my vps are down so ive been told to use the opendns ones. Easy right, edit resolv.conf. I do that, reboot.. the files changed back. So i edit dhclient.conf and add supersede (also tried prepend) domain-name-servers xx,xx; Reboot, its changed back so i go into /etc/sysconfig/network-scripts and edit the two files vnet0 and vnet0:0 (2 ip's) and add PEERDNS=no. Reboot, resolv.conf and the two files ive edited have changed back to orginal. Im pulling my hair out since i cant resolve anything to send emails etc, and its starting to feel alot like groundhog day.
Manually edit /etc/resolv.conf and then chatter +i /etc/resolv.conf Makes it unchangable, even by root, unless you chatter -i /etc/resolv.conf Might also want to think about installing bind as a caching only nameserver, then you can just reference localhost.
Done that.. Code: sudo cat /etc/resolv.conf #search lan nameserver 208.67.222.222 nameserver 208.67.222.220 ryanmt@vps:~$ ping google.com ping: unknown host google.com ryanmt@vps:~$ ping 208.67.222.222 PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data. 64 bytes from 208.67.222.222: icmp_seq=1 ttl=58 time=1.44 ms 64 bytes from 208.67.222.222: icmp_seq=2 ttl=58 time=1.45 ms --- 208.67.222.222 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 1.449/1.453/1.458/0.038 m any ideas?
This is normal if your server is a vserver based on openvz or virtuozzo. You have to ask your provider to change the dns servers in the virtualisation software.
Well I was using hypervm but it got hacked so im not sure what its setup with now. Will have to mither live support more. Thanks
