Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am a Linux server newbie. I set up Fedora Core 3 on an old box. I've managed to get http (apache), ftp, and remote ssh to work. My goal for this box is for it to be my local test location (on my LAN) for building webpages that I can later upload to the internet.
Set up your own DNS server if you want to do it for a whole LAN. If you're just doing development from one workstation, just add the domain to /etc/hosts with the server's IP. Don't forget to remove it when you move to the real server or you will have no end of headaches.
i would recommend the host file, if its just for one record; this will by far be the simplest way. setting up an entire bind, while a good learning excercise, is like using a 12 guage to kill al cockroach.
That's what I kind of thought. But that brings up a slightly different question.
I have my server where the website is located for construction. And, I have this computer I am writing on, and where I will access that local copy of the website from the server to work on it.
Both of these computers are assigned IPs by my Linksys router. However, they are currently being handed out dynamic IPs. Thus, every time the IP of my server changed I would have to go into etc/hosts/ and change that line of the file you just explained to me.
Of course, I could do that. But it would be easier if I could assign a static IP to my server so I only had to set the file once. I know it can be done because I have done it with a Win XP system on the Linksys router. But I don't have a GUI on my server and I have no idea how to give the server a static IP.
Any chance you could explain that to me, or will I have to edit my etc/hosts file once a day?
Maybe it would just be easier to set static IP for the entire LAN at the Linksys end of things. I know how to do that.