Re: MACHINE NAMES
From: houghi (houghi_at_houghi.org.invalid)
Date: 07/31/05
- Next message: Roy Schestowitz: "Re: Formatting Hard-drives and Recovery"
- Previous message: houghi: "Re: setting time from server."
- In reply to: Karel Venken: "Re: MACHINE NAMES"
- Next in thread: Karel Venken: "Re: MACHINE NAMES"
- Reply: Karel Venken: "Re: MACHINE NAMES"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 31 Jul 2005 05:27:02 -0000
Karel Venken wrote:
>
> I guess it depends. If you have an officially registered domain, you
> could use this one, if not, I thend to use a generic setting, like
> choosing preserved private IP-adresses 10.x.x.x. In most cases I
> configure something like local.net.
Why local.net? Why .net at all? Just name it local.
> So names become pc001.local.net,...
The name would become pc001.local
> The local.net(*) makes me -this is my own convention- clear that it is
> an unofficial local choice and should not expect to be known by any
> other DNS.
Well, you are wrong and do you know why?
> local.net also follows the toplevel, sublevel convention in
> domainnames. Although I agree that it is fun to make your own names.
>
> (*) It is registered btw. :-(
Because of this. Just make up your own TLD for internal use if you think
you need TLD and domain. In most cases something like familyname shoudl
be enough. (The English have the luck that the house names can be used
sometimes. :-)
So in you case it would become pc001.venken, pc002.venken, ...
Now if you have an extremely large company (or family) r very large sets
of PC's for each familymember, you could start working with
pc001.karel.venken, pc002.karel.venken, pc001.jan.venken
pc002.jan.venken, ...
However normaly there is no real need for such a thing and in a company
or private situation, you could leave the venken out in the second
example
I know the person who owns localhost.be and you will be amazed how many
(test) emails he gets. I can imagine that the same will happen if you
have local.net as your own internal domain and try to send mail
internally.
Really, if you have need for something in two parts (and techicaly you
can perfectly do without) just work with vinken.local or if you think
you need three letter, vinken.loc or two vinken.xx or whatever. However,
never, ever, never use a valid domain that would work outside, if you do
not own it.
> In most cases I don't bother to fantasise names. I just append the
> IP-adress ciphers -which are unique btw.- to a prefix. Except for hosts
> which have a clear server function, like www, gate. In this case, when
> hosts swap designations, I can keep the same names and be sure that
> services continue. Lets say that at some point in time host 10.0.0.111
> is a webserver, it will be called web in domain local.net, thus
> web.local.net (and also pc111.local.net). Now, lets say that, due to too
> much popularity (of the single other host in the network), I need to
> replace it by a more powerfull machine, I just rename this one
> pc111.local.net and call the new one with IP-adress 10.0.0.102
> web.local.net. After reading the RFC I realize now that I am not
> following it, but if you have 1000 hosts (I don't, sniff...), giving
> them all fancy names does not help much. You won't remember them anyway.
What happens is that they are given two names. One personal name and one
purpose name. (I hope I explained why not to name them local.net. Please
don't)
You see this most of the times with services like pop and smtp. Now in
your example of a webserver that needs an upgrade. Your IP 10.0.0.1 is
linked to www.local.loc and you need a bigger machine. There are several
ways to do this. What you do is pull out the old machine and put in the
new. I will follow this. Other peopel will not see many problem.
Now how do people with 1000+ machines do that? First they will use the
subnets available by the use of 10.x.x.x. They could for example use
10.x.1.x for web, 10.x.2.x for mail, 10.32.x.x for machines in Belgium,
10.44.x.x for machines in the UK, 10.49.x.x for German machines or
whatever they choose to do.
Now they have a webserver in Belgium that needs to be changed. People
surf to that serve by http://www.belgium.loc and it has the IP 10.32.1.1 and
needs to be changed.
What it is they do is put in the second server at 10.32.1.2 and testrun
that for a bit. Now what they ALSO do is give it a second name. This can
be done in a very boring way www02.belgium02.local. This can also be
done by giving itany other name. like, the use of the periodic table,
starwars or trek names, beernames, ...
Now when they decide that the second server is good for production, they
just change the DNS so that http://www.belgium.loc points to 10.32.1.2.
Advantages. For the user no disconnecton. Fir the sysadmin clear
different machinenames either by name or number. Remember a lot of
companies have several servers for www or other things. Servers mostly
get named by sysadmins. Personal PC's in offices mostly not. The reason
is that it is easier to remember a name then a number.
So you are right, gicing 1000 PC's a fancy name is not good. Giving
several of them fancy names is a good idea.
-- houghi http://houghi.org > Knock-knock. > Who's there? > Under the Patriot Act, we don't have to tell you that.
- Next message: Roy Schestowitz: "Re: Formatting Hard-drives and Recovery"
- Previous message: houghi: "Re: setting time from server."
- In reply to: Karel Venken: "Re: MACHINE NAMES"
- Next in thread: Karel Venken: "Re: MACHINE NAMES"
- Reply: Karel Venken: "Re: MACHINE NAMES"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
