Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
I have a Fedora Core 7 server that loses its DNS settings on system reboot. The /etc/resolv.conf file does not maintain its entries even though they are entered by the root user.
The workaround that I have implemented involves the resolv.conf file saved under a different name, and a symbolic link under the appropriate name pointing to the other file. While this works, it does not fix the original problem.
Has anyone seen this, know what the cause is, and how it can be fixed? Thanks.
Reviewing the /etc/sysconfig/network-scripts/ifup-eth0 script I see refrences to /etc/dhclient-${DEVICE}.conf.
This suggests it is using per device dhclient.conf files (e.g. dhclient-eth0.conf).
In the directory mentioned above have a look at your ifcfg-eth0 (or eth1 or eth2 etc... depending on which interfaces you're using) to see if you have "BOOTPROTO=dhcp" in the active ones. Then look for the device specific dhclient.conf files.
Also in above I notice a reference to the default /etc/dhclient.conf being allowed for generic purposes so you can probably create one if necessary. It likely isn't there because it is allowing for device specific ones.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.