1 |
On Sat, Mar 03, 2007 at 03:21:52PM -0600, Dan Farrell wrote: |
2 |
> On Sat, 3 Mar 2007 22:04:59 +0100 |
3 |
> "Michal 'vorner' Vaner" <vorner@×××.cz> wrote: |
4 |
> |
5 |
> > Hello, |
6 |
> > |
7 |
> > On Sat, Mar 03, 2007 at 11:17:52AM -0800, Bob Young wrote: |
8 |
> > > Obviously on a given system each NIC is usually connected to a |
9 |
> > > different domain, my question is, whether or not it |
10 |
> > > is /legal/possible/okay to use different *hostnames* on different |
11 |
> > > NICs? |
12 |
> > |
13 |
> > AFAIK, you can have multiple names for one IP and multiple IPs for one |
14 |
> > name (there are more ways to do that). So, I see no reason why anyone |
15 |
> > would ever forgive you to have different name for each of IP addresses |
16 |
> > your computer has. The other question is if you really want to do |
17 |
> > that, because there might be applications not expecting your computer |
18 |
> > is "schizophrenic" in such way and go nutty. |
19 |
> > |
20 |
> > With regards |
21 |
> > |
22 |
> on the contrary, there are good reasons to have more than one name for |
23 |
> a single computer. For example, say I have a server 'zeus.mydomain' |
24 |
> that also does mail. If I name the mailserver 'mail.mydomain' then I |
25 |
> can CNAME that to zeus.mydomain via DNS, or I can just set |
26 |
> mail.mydomain to the ip address of the second interface. Result - I |
27 |
> can redirect my mail to mail.mydomain and it can go to whatever |
28 |
> computer I desire, whether or not it has different names. 'zeus' is |
29 |
> still listening under that name for other requests. If i use 'zeus' |
30 |
> for heavy filesharing, I can still get good access over a non-saturated |
31 |
> ethernet device on 'mail'. |
32 |
|
33 |
Well, this is something else - the computer knows itself as zeus and has |
34 |
"nicknames". However, if I got what the question was about - to be name1 |
35 |
for one card and name2 for the second - and do not appear as name2 on |
36 |
the first at all. |
37 |
|
38 |
IMO machine should have the same "base" name to any domain it shows in - |
39 |
the one that it shows in bash command prompt. Then you can have |
40 |
additional names for the services and they can differ. |
41 |
|
42 |
But the name showed on the bash should probable be reachable (if |
43 |
possible) from any network it appears on. The situation shown here is |
44 |
probably odd (the names here are the only ones there, no additional ones |
45 |
or base ones). |
46 |
|
47 |
[ X ] C1 ---- C2 [ X ] C1 ---- C2 [ X ]. |
48 |
|
49 |
The [ X ] is a machine, ---- is a network and those C? are names of the |
50 |
machine on the net. Now, ping C1 on the middle machine. Should it ping |
51 |
itself on the right interface or look for the left computer? You should |
52 |
at last have something like: |
53 |
|
54 |
[ Name1 ] C1 ---- C2 [ Name2 ] C1 ---- C2 [ Name3 ] |
55 |
|
56 |
(even if Name2 could not be resolved by the DNS on the right network for |
57 |
example). |
58 |
|
59 |
And you can "nickname" Name2 as mail or ntp if it suits you. |
60 |
|
61 |
I hope I made myself clear and I apologize for the previous |
62 |
misunderstanding. |
63 |
|
64 |
Have a nice day |
65 |
|
66 |
-- |
67 |
Anyone who goes to a psychiatrist ought to have his head examined. |
68 |
-- Samuel Goldwyn |
69 |
|
70 |
Michal 'vorner' Vaner |