Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Edited out in favor of Firerat's soution, thanks Firerat for pointing this one out, I always use static IP adresses on my LAN's, so the phenomenon of a changing resolv.conf never happened to me...
I learned something here! Thanks dude
Thor
Last edited by ButterflyMelissa; 06-12-2013 at 03:16 PM.
'resolv.conf's should push and pop in an orderly fashion, so if you are saying that you make a change and then it permanently disappears, then something odd is happening. On the other hand, if, when some application such as NetworkManager or Wicd takes control of networking, you temporarily see something unconnected to what you originally set, then that is expected behaviour. But along with this expected behaviour, you should see some note along the lines of "### altered by network manager...do not edit" and probably a date/time that this last happened.
While NM/wicd are in control, any settings available from DHCP/mDNS might turn up in the file, although you can probably reconfigure them to only take selected parts of the information.
If, of course, you did edit the file while it had the "do not edit" comment present, you should expect things to go wrong, even if you don't know quite how soon this should happen.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.