Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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'm a bit of a nub with linux, but somehow managed to find myself building a DHCP server. The machine has twin network cards (Intel 80003ES2LAN's), one of which (eth0) I want to set custom DNS for, and the other (eth1) will get its info automatically. The issue I'm having is that when both interfaces are set to auto obtain settings, everything works fine. After entering DNS info manually on eth0 and restarting the network, eth1 has no connectivity. NetworkManager is disabled and I'm using the "old" network system. Any ideas on what I'm missing here?
Last edited by winginit_118cl; 05-21-2008 at 12:22 PM.
Nope. In fact, eth0 isn't even wired in. When I restart the network, both interfaces are brought up ok...just can't hit the server or access the internet through eth1, which is plugged in.
I had a few networking issues with F9, and switched to network-manager which seemed to solve my problems.
That said, for a server, Fedora really isn't the right choice - too bleading edge, release cycle too short, etc. Try CentOS - if you know Fedora, you'll know CentOS (it's unbadged RHEL)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.