From: Dan Farrell <dan@spore.ath.cx>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A DNS question.
Date: Sat, 3 Mar 2007 15:21:52 -0600 [thread overview]
Message-ID: <20070303152152.6020224e@pascal.spore.ath.cx> (raw)
In-Reply-To: <20070303210459.GD1729@tarantula.kolej.mff.cuni.cz>
On Sat, 3 Mar 2007 22:04:59 +0100
"Michal 'vorner' Vaner" <vorner@ucw.cz> wrote:
> Hello,
>
> On Sat, Mar 03, 2007 at 11:17:52AM -0800, Bob Young wrote:
> > Obviously on a given system each NIC is usually connected to a
> > different domain, my question is, whether or not it
> > is /legal/possible/okay to use different *hostnames* on different
> > NICs?
>
> AFAIK, you can have multiple names for one IP and multiple IPs for one
> name (there are more ways to do that). So, I see no reason why anyone
> would ever forgive you to have different name for each of IP addresses
> your computer has. The other question is if you really want to do
> that, because there might be applications not expecting your computer
> is "schizophrenic" in such way and go nutty.
>
> With regards
>
on the contrary, there are good reasons to have more than one name for
a single computer. For example, say I have a server 'zeus.mydomain'
that also does mail. If I name the mailserver 'mail.mydomain' then I
can CNAME that to zeus.mydomain via DNS, or I can just set
mail.mydomain to the ip address of the second interface. Result - I
can redirect my mail to mail.mydomain and it can go to whatever
computer I desire, whether or not it has different names. 'zeus' is
still listening under that name for other requests. If i use 'zeus'
for heavy filesharing, I can still get good access over a non-saturated
ethernet device on 'mail'.
nevertheless, such a thing would really better be accomplished with
ethernet bonding and CNAMEs in dns configuration.
another, more reasonable situation might be a computer that routed a
few subnets and also provided other services to a subnet or two. It
might also have an external interface to the ISP, whose hostname on
that network is not up to you. I don't want to use "c-24-245-14-14"
as the name for my internet gateway on the inside, do i? Similarly, on
subnet A it might make perfect sense to call it 'gateway.a.domain' but
perhaps such a computer -- another internet gateway, perhaps? already
uses that name on subnet B. In that case, imight want to name the same
computer router.b.domain since it routes traffic from b to a.
make sense? correct me if i'm wrong ; )
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-03-03 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 19:17 [gentoo-user] A DNS question Bob Young
2007-03-03 20:48 ` Dan Farrell
2007-03-03 21:04 ` Michal 'vorner' Vaner
2007-03-03 21:21 ` Dan Farrell [this message]
2007-03-03 22:16 ` Michal 'vorner' Vaner
2007-03-04 0:49 ` Bob Young
2007-03-04 9:20 ` Michal 'vorner' Vaner
2007-03-04 17:52 ` Dan Farrell
2007-03-04 18:13 ` Michal 'vorner' Vaner
2007-03-03 21:43 ` Paul Colquhoun
2007-03-03 23:57 ` Reuben Farrelly
2007-03-04 17:25 ` Dan Farrell
2007-03-03 22:21 ` David Relson
2007-03-08 5:54 ` [gentoo-user] " David Talkington
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070303152152.6020224e@pascal.spore.ath.cx \
--to=dan@spore.ath.cx \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox