public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bob Young" <RKY@Sonic.Net>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] A DNS question.
Date: Sat, 3 Mar 2007 16:49:48 -0800	[thread overview]
Message-ID: <016801c75df7$03600c40$08200a0a@PowerMoneySex.Lan> (raw)
In-Reply-To: <20070303221647.GE1729@tarantula.kolej.mff.cuni.cz>

I appreciate all the replies, and yes Michael you're correct the original
question was in regards to a system having different "base" (host) names for
different NICs. IOW the Windows Domain Controller that eth0 is connected to
records eth0 in it's DNS table as gentoo.windowsdoman.local. In addition in
/etc/make.conf the the following is declared:
eth0_dns_domainname="windowsdomain.local" and
eth0_nis_domainname="windowsdomain" no nis or dns domainname is declared for
eth1 or eth2 as that causes problems. I'll probably also configure BIND to
act as a secondary DNS for the domain controller listing on eth0 and eth1.

Now with regards to eth1, it is my intent to configure eth1 as with the
machines only public IP address (69.12.134.79), and configure BIND to listen
on eth1 as a secondary domain name server, the primary domain name server
would have an "A Record" for 69.12.134.79 and it would be named
ns.somedomainname.com. IOW it would have a different "base" name (ns) than
eth0 (gentoo). My question is whether or not this is valid/"legal"/okay,
i.e. is it likely to cause any problems?

I did see Ruben's comment about named "views" and it looks like that may be
something to investigate.

Any further comments/suggestions welcome.

Thanks,
Bob Young
San Jose, CA



-----Original Message-----
From: Michal 'vorner' Vaner [mailto:vorner@ucw.cz] 
Sent: Saturday, March 03, 2007 2:17 PM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A DNS question.

On Sat, Mar 03, 2007 at 03:21:52PM -0600, Dan Farrell wrote:
> 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'.  

Well, this is something else - the computer knows itself as zeus and has
"nicknames". However, if I got what the question was about - to be name1
for one card and name2 for the second - and do not appear as name2 on
the first at all.

IMO machine should have the same "base" name to any domain it shows in -
the one that it shows in bash command prompt. Then you can have
additional names for the services and they can differ.

But the name showed on the bash should probable be reachable (if
possible) from any network it appears on. The situation shown here is
probably odd (the names here are the only ones there, no additional ones
or base ones).

[ X ] C1 ---- C2 [ X ] C1 ---- C2 [ X ].

The [ X ] is a machine, ---- is a network and those C? are names of the
machine on the net. Now, ping C1 on the middle machine. Should it ping
itself on the right interface or look for the left computer? You should
at last have something like:

[ Name1 ] C1 ---- C2 [ Name2 ] C1 ---- C2 [ Name3 ]

(even if Name2 could not be resolved by the DNS on the right network for
example).

And you can "nickname" Name2 as mail or ntp if it suits you.

I hope I made myself clear and I apologize for the previous
misunderstanding.

Have a nice day

-- 
Anyone who goes to a psychiatrist ought to have his head examined.
		-- Samuel Goldwyn

Michal 'vorner' Vaner

--
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-03-04  1:00 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
2007-03-03 22:16     ` Michal 'vorner' Vaner
2007-03-04  0:49       ` Bob Young [this message]
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='016801c75df7$03600c40$08200a0a@PowerMoneySex.Lan' \
    --to=rky@sonic.net \
    --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