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 building a webserver / email server, for personal uses, that will be directed to the outside world. My question upon building this server is something I for the first time pondered. I'm wondering if you can make your full hostname just your "domain" name?
just putting in
this way it matches your www address? Does it really have to have a 3 part system?
Are there any draw backs to use using your domain name?
www.domain.com is a service. davesserver.domain.com is a machine name, and they are used in different ways, and what you're asking seems very much unnecessary. to "match" www. you configure whatever server software your using, e.g. apache for http services, to respond to that name. It's inconsequential what the name of the actual tin is.
Thanks!,, I was just wondering if you would actually run into any problems by creating the host name as just server.com instead of it being something like computer.server.com when it came time to registering it to a web address. It was just a passing thought as I was building my server and I realized, I don't know. As in a Microsoft world if your building a domain controller, you don't have the ability to "not name the server" and just reference the domain as the server. Were as in a Linux world the OS doesn't seem to really care.
But I see what you mean as those two wouldn't have any type of relationship to each other at all since they don't identify with each other in that way. At the time that I wrote the question I didn't consider the angle that the service doesn't even recognize the computer name or internal dns, it just looks for the external ip.