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!
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.
They are just the default values given to your machine. Since you aren't on a domain, the system doesn't care what the values actually are (since they essentially have no meaning in a single-computer environment - no need for a unique identifier) and the network config defaults to using "localhost" and "localdomain".
Domain names don't just apply to the internet; they apply to an intranet as well. The difference is that internet domain names and the IP address they correspond to are registered on publicly accessible DNS servers (domain name server ) which can resolve said domain name to the actual machine's IP address whenever someone's browser requests it. Domains which are local to your network aren't registered publicly, and therefore are only accessible to your local network (your router typically acts as the dns server in this case).
However...even on your local network, the network still needs to be able to uniquely identify each computer. Think of it this way - you have two computers, both named "localhost@localdomain", and you want to ssh into one of them...what's a poor router to do? Hence, the need for unique hostnames.
You can change both values if you like. I believe that RedHat has the netconfig command... If not, it will have some GUI network config utility. I usually change my hostname to something more descriptive (if nothing else, so that I can tell my PuTTY sessions apart ) using the command 'hostname' (as root).
[Sorry if this is rambling/slightly inaccurate. I didn't actually consult wikipedia or google while writing this.]
Last edited by rose_bud4201; 06-07-2005 at 10:17 PM.
The first name can be anything unique to the others.
The second Hostname must be the same across the network.
And the .com could be .org , .com.au , or whatever.
What if I had those 3 machines and I wanted to HOST a webpage from one of the PC's say pc1, what if someone visits homeserver.com but some other comapny has registered homeserver.com? How does this work?
p.s - sorry for the late reply I have been flat out
You're pretty close, yup. Firstly, the "." is a sort of hierarchy-delimiter; it separates individual pc names from the domain name from the upper-level domain. Because your personal network is likely to be small enough that you can keep a handle on it without the upper-level grouping, you don't really need the ".com, .org, .au" part. You can certainly have it, but it won't have any special meaning (and in fact, it doesn't. Unlike public URL's, anything after the PC name gets lumped into the domain name. So whereas yahoo's domain name is "yahoo", yours would be "hostname.com").
Now - you certainly can make your domain "hostname.com", but that does _not_ constitute a DNS entry and that will not make your network publicly accessible. I could call my home network yahoo.com all I wanted, it won't ever matter. That network is only visible to your router/switch/hub whatever and the computers it controls.
Publicly-accessible DNS entries are gained by you paying someone for a domain name, and they go and register that domain name and the IP address of the computer hosting the website (or whatever it is). If I tried to register yahoo.com, someone would most certainly complain
So, if you wanted to host a website on your own server, you could either a) use your modem's IP address and tell your router to forwads requests coming in on port 80 to your particular pc, b) pay your ISP for a static IP address, set up apache and then register a hostname and your IP address, or c) use a service such as dyndns which will give you a publicly accessible URL while you still have a dynamic IP (it'll update its own DNS entries whenever your IP changes. And while the IPs given to cable modems rarely change, they definitely do).
Hopefully this isn't too rambling...
Last edited by rose_bud4201; 06-11-2005 at 07:04 PM.
Rose-Bud no shit you are a master, do you know how much crap I have read looking for the answers you have given me so clearly.
Have you ever written any tuts or papers on any aspect of computing? if not you should.
Have you a website? I would love to check it out.
That makes sense to me apart from one thing - If I was running BIND what would happen if I configured it with yahoo.com pointing to my static IP? Can that be done? I have heard of running your own DNS server so doesnt that bypass the registering process? Say I registerd rosebud.com and I own it I could use BIND to tell the big name servers where I am on the net correct?
Well....you *can*, but even though you're running your own DNS server you still have to ask your ISP to enter whatever external names you want (and the name of the box you're using as your DNS box) into their name server. No matter what, you're not a publicly available network on your own..you still go through your ISP. And if they're silly enough to try to give you yahoo.com, they're going to be in a hell of a lot of trouble when the big public DNS servers start trying to resolve that one...
What would happen is this - it would sort of work, for a little while. You would probably be getting packets going to both the real Yahoo and your box, because the new domain would be overwritten to point to you in some of the public dns servers, and would still point to 220.127.116.11 (Yahoo) on others. So depending on where the packets originated and which address the routers in between saw as pointing to "yahoo", the packets would go to one server or the other. These things take time to propegate through all of the DNS servers (which is why when you register a domain name with a provider, they usually tell you to wait 24 hours before expecting things to be perfect), but you could still fudge things up pretty quickly.
In any case, your ISP would probably tell you something rude if you asked them to use a domain name that was already taken. And if they didn't catch it first, the federal agencies that control the registering of domain names (there's 1 in every country) would find you pretty quickly to err..."correct" things
There used to be a decently big phenomenon of sites offering "Windows Accelerators"...sort of like download accelerators, I guess...Apps that were supposed to make your computer run faster. I don't know if they did anything but open all of your ports to pr0n email spammers, but that's a matter of debate.
However, I'm more in agreement that the best windows accelerator is gravity, or in other words Windows is at its best when it's just been thrown out of a 30-story building