Original post after Update of info:
> Sorry,
> I guess my original post confused several people, I will try and
> give more precise explanation.
>
>
> >Hello Managers,
>
> > I have a question about adding a new segment on my network.
> > The Network layout looks something like this.
> ____
> |____| C
> ____ ____ _________ / ____
> >-----|____|-----|____|--------------------|_________|--- --|____| D
> A B long thinnet Bridge \____
> | |____| E
> __|__
> |_____|Modem
> /
> /--------\
> / World \
> | dial-up |
> | internet |
> | Service |
> \__________/
>
> >My layout here is that I have node B as a gateway to internet and is also
> >the mailhost for the whole domain. All machines mount node B /var/spool/mail
> >and mqueue and everything is working fine. Now there are about 10 users that
> >are moving to the end of the "long Thinnet" and I will be moving there home
> >directories and openwindows plus database server down to machine E SS10 with
> >two external Gig(s). There will be very little bridge traffic. I also will
> >probably make node E a NIS server from master NIS (node A). Eventually
> >management wants to make Nodes C,D,E,...(n) part of a different domain.
>
> >Question:Should I spend the time now to make them ther own domain. Will it be
> >difficult later to change.
>
> >Question: If I change now will I spend A life time trying to work through all
> >the Domain name server issues and mail gateways and sendmail.XX this and that.
>
> >I guess I am looking for more war stories and helpful hints as System Admins
> >one of many hats that I wear and I don't want to be hacking at this too long.
>
> >I really would appreciate any suggestions or pointers.
>
> >If I sense there is a need for a summary I will.
>
> Thanks!
>
> Well first I am not a registered NIC site, we get are email and access to
> internet through PSI. We just grabbed 192.9.200.XX for our series of IP
> numbers. The biggest goal out of moving people is to provide a self-sustained
> network environment for our developers. Initially I planned to keep everyone
> in the same IP family. Our domain is osi.com. I would like to get to a point
> where I have the new segment with domain name of dev.com with ip address of
> 193.9.200.xx. I would also like to keep the mailhost being Node B on original
> segement. From what I understand I do not need a router as long as the new
> segment is on the same class of IP addresses. The bridge we purchased is the
> Black Box Local ELS bridge.
>
> I hope that this is clear enough!
>
> Derik Jarne
> Systems Engineer
> Objective Systems Integrators
> 916-989-7340
> derik@osi.com
>
>
> ----- End Included Message -----
>
>
______________________________________________________________________________
Well I got quite a few interesting responses that seemed to run the Full
spetrum of NO IT ALL(s)... I appreciate it!.
The best answer came from Stern at Sun EAST..Thanks Hal! (The law does still
apply) KISS!
if you're only pushing mail and the occasional NIS request
through the bridge, don't bother spinning up a new domain.
changing mail routing and duplicating passwd, hosts, aliases
and other invariant information will be far too much work.
--hal
The rest will be included for full disclosure of data:
----------------------------------------------------------------------------
steven@cell.BIH.Harvard.Edu
alas, i have no suggestions, but i am extremely interested in a summary
of responses. thank you.
Steven L. Blechner
Director, Molecular Computing
Beth Israel Hospital
Boston, MA
----------------------------------------------------------------------------
Eckhard.Rueggeberg@ts.go.dlr.de
> Eventually management wants to make Nodes C,D,E,...(n) part of a
> different domain
What do you mean ?
- Different physical ethernet domain,
- different NIS domain or
- different DNS subdomain ?
To be more specifically : What will get different ?
- More than the last byte of the internet number
- The names the two NIS servers should propagate
- The subdomain part of the Internet mail adress
All these three are totally uncorrelated to each other
For the first, you need a Gateway instead of a Bridge, either a
true dedicated one or a workstation with two (or more) ethernet
cards, and the only thing wich changes on the other machines is
routing, but that's trivial.
For the second, you only have to change the /etc/defaultdomain
on the affected machines and nothing else.
For the third, you'll in fact get some DNS-Problems, but sendmail
should be no problem.
Hope this helps
>> Thanks Eckhard!..I guess you didn't get the question..
------------------------------------------------------------------------------
stefan@centaur.astro.utoronto.ca
Unless you are going to have MANY machines (like, over 200), or
long-distance links, then your single subnet is just fine, especially
since you say not much traffic crosses the bridge. (As for bridges,
I heartily recommend PC-ROUTE). I would suggest that your management
be convinced to take this tack.
Note that
DOMAINS and SUBNETS are NOT the same thing. For example, in my Astronomy
Department, we have the domain astro.utoronto.ca scattered over
three geographic locations 25km apart, on at least 4 subnets. Network
addressing and routing are not the same as domain naming; the nameserver
database is where the two schemes are cross-referenced.
So if your management for political reasons wants separate domains,
there is nothing to prevent setting up your nameserver data that way
(and /etc/hosts ...). You can still keep it all on one SUBNET with
one IP subnet number (if Class C).
> Question: If I change now will I spend A life time trying to work through all
> the Domain name server issues and mail gateways and sendmail.XX this and that.
>
Sure. I bet 90% of all sysadmin time is spent resolving e-mail issues ...
------------------------------------------------------------------------------
Christian Lawrence <cal@soac.bellcore.com>
..... maybe you weren't/aren't considreing this but .....
NIS+ supports hierarchical domains. if you use NIS+ you can have each leg
be a subdomain .... an interesting concept (similar to DNS in some respects)
that seems to fit in many instances including yours. I believe you can
retrieve the NIS+ 4.x binaries off of a Solaris 2.x CD !!
Then if you ever go to 2.x you have already gotten over that pain !
>>Thanks Christian...I'll look into this....!
------------------------------------------------------------------------------
Unfortunately, you can't do this. You will need to requrest an
"official" network for osi.com. 192.9.200.xx is owned by CDC :
Central Data Corporation (NET-CENDATA)
1602 Newton Drive
Champaign, IL 61821
Netname: CENDATA
Netnumber: 192.9.200.0
Coordinator:
McGrath, Robert (RM524)
cendata!cendata!mcgrath@uunet.uu.net
(217) 359-8010 ext. 247
Record last updated on 10-Jun-91.
and 193.9.200.xx is owned by :
RIPE NCC (NETBLK-RIPE)
Kruislaan 409
NL-1098 SJ Amsterdam
THE NETHERLANDS
Netname: RIPE-CBLK
Netblock: 193.1.1.0 - 193.254.254.0
Coordinator:
Karrenberg, Daniel (DK58) dfk@ripe.net
+31 20 592 5065 Voice +31 20 592 5090 Fax
Record last updated on 12-Aug-92.
Also, a bridge basically makes all the nodes appear to be on the same
network segment ( in this case 192.9.200.xx ). You would have to ad
>>My point exactly!
a router to have separate networks ( if that is what you want ). It
has nothing to do with the "class" of the network, only the same
network. I think I would request 2 official network numbers from the
NIC and plan on changing over net topology initially to have a single
class c "official" network number ( different from 192.9.200 ). If
you decide to add a router to the topology and thus have separate
network for the 3 other hosts (c,d,e), then you would have to contend
with running NIS over separate networks ( we do that today anyway --
shouldn't be hard ).
As for the difficulty of changing your mail setup. You appear to be
MX's from psi, as show below:
Objective Systems Integrators (OSI-DOM)
1002 River Rook Drive, Suite 221
Folsom, CA 95630
Domain Name: OSI.COM
Administrative Contact:
Schoffstall, Martin (MS9) SCHOFF@PSI.COM
(703) 620-6651
Technical Contact, Zone Contact:
Zort, Robert (RLZ3) zort@uu.psi.com
(518)283-8860
Record last updated on 11-Jul-91.
Domain servers in listed order:
NS.PSI.NET 192.33.4.10
NS2.PSI.NET 192.35.82.2
As a result, that shouldn't be too difficult, since you are not
already known as a specific ineternet address. I'd take the plunge.
Do some reading and planning though before you start.
} I would also like to keep the mailhost being Node B on original
} segement. From what I understand I do not need a router as long as the new
} segment is on the same class of IP addresses. The bridge we purchased is the
} Black Box Local ELS bridge.
As I said above, if you route, you need a router regardless of whether
the network class is a, b, or c.
If I were you, I'd start reading up on sendmail, mail, and DNS. There
are some excellant books on the subjects.
-- Jim Ray Harris Semiconductor Internet: jdr@semi.harris.com PO Box 883 MS 62B-022 Phone: (407) 729-5059 Melbourne, FL 32901>>WOOOOOOOW Jim....I think you also missed the point. Thanks anyway...
>>I`ll wait for the movie...
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:23 CDT