Date: Sat, 9 Feb 2002 12:07:50 +0300 From: Odhiambo Washington <wash@wananchi.com> To: raiden23@netzero.net Cc: FBSD-Q <freebsd-questions@freebsd.org> Subject: Re: Domain mail question Message-ID: <20020209090750.GD32600@ns2.wananchi.com> In-Reply-To: <4.2.0.58.20020208155526.0098ee20@pop.netzero.net> References: <4.2.0.58.20020208155526.0098ee20@pop.netzero.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Lord Raiden <raiden23@netzero.net> [20020209 00:02]: wrote:
> Ok, I'm deathly curious about this. Since we're going to be doing
> some more consolidating sometime soon again I'm curious about
> something. Personally I've never had to do this so I have zero experience
> with this. Right now we're running one domain per server, hence one mail
> domain per server. But what I'm looking at doing to reduce the number of
> active servers is to take a group of our smaller sub-domain's and combine
> all of the POP3 and SMTP mail services, apache/IIS, and Samba services and
> port them all to one FreeBSD 4.5 machine. Now here's the catch.
My domain is wananchi.com
I have several subdomains (actually just FQDN like alligator.wananchi.com), so in
DNS (zone file for wananchi.com)
@ IN MX 5 mail.wananchi.com
@ IN MX 10 mx2.wananchi.com
alligator IN A 62.8.64.108
IN MX alligator.wananchi.com.
That way I have all mail for *@alligator.wananchi.com going straight to it.
That's not the only way to do it but I don't understand what you mean by
"take a group of our smaller sub-domain's and combine all of the POP3 and
SMTP mail services, apache/IIS, and Samba services and port them all to
one FreeBSD 4.5 machine" - you mean several domains or just subdomains?
Both ways it will work but you should be clear on this since initially you
said you run "one domain per server".
> Part of them are NT/2000 boxes. The part about moving those over
> I'll figure out on my own. What my question is, is how do you run multiple
> domains off of one server? Like where before you had each domain on a
> separate server all by themselves, I need all of those domains to all point
> to one machine. Here's the basic list of what I am wanting to do.
Simple. Just DNS config for the domains. If you need more help lemme know.
>
> 1. Have up to 23 different network names all pointing to one
> machine. AKA when you type "\\guarvo" or "\\skywalker" as the network
> machine name, I want them to all go to one machine rather than each
> individual machine.
DNS again. Easy. You're saying that if you ping,
wash@ns2 ('tty') ~ 1 -> ping alligator
PING alligator.wananchi.com (62.8.64.108): 56 data bytes
64 bytes from 62.8.64.108: icmp_seq=0 ttl=64 time=0.715 ms
64 bytes from 62.8.64.108: icmp_seq=1 ttl=64 time=0.593 ms
wash@ns2 ('tty') ~ 3 -> ping courier
PING alligator.wananchi.com (62.8.64.108): 56 data bytes
64 bytes from 62.8.64.108: icmp_seq=0 ttl=64 time=0.731 ms
64 bytes from 62.8.64.108: icmp_seq=1 ttl=64 time=0.607 ms
So requests to either courier or alligator are directed to
62.8.64.108 - that's called CNAME in DNS.
> 2. I want things for the internal web to work the same way. So
> that "staff.domain" and "sales.domain" and "shipping.domain" all have their
> own unique IP address's, yet all point to the same machine.
So one machine will have multiple addresses assigned to one network interface, yes?
They can have unique NAMES yes, but still point to the same box. That's a second
way of doing it. If you mean www.sales.domain and www.shipping.domain that's even
easier to do in Apache.
> 3. Same thing for mail. So when a user types in "mail.domain1" for
> their outgoing mail server, or incoming, either one, and another user types
> in "pop.domain3" they both are getting their mail from the same server,
> even though the IP's resolve differently.
Again same as having multiple IPs on one network interface on one box.
That is a waste of IP addresses.
>
> In sort I guess what I'm asking for is to figure out how to make it
> so that one machine can take on up to 250 unique IP's and/or identities,
> and keep them all straight and separate so that the one machine actually
> looks like as many as 250 other machines. The idea is to consolidate as
> many machines as possible into one without any interruption in service to
> the users and it needs to be as seamless as possible so that nobody knows
> the difference come monday morning.
That's a waste of IPs. There is no ONE single tutorial for this. You will have
to master several apps that provide different services, SMTP daemon, POP3 daemon,
Web server, Samba, etc.
-Wash
S y s t e m s A d m i n.
--
Odhiambo Washington <wash@wananchi.com> "The box said 'Requires
Wananchi Online Ltd. www.wananchi.com Windows 95, NT, or better,'
Tel: 254 2 313985-9 Fax: 254 2 313922 so I installed FreeBSD."
GSM: 254 72 743 223 GSM: 254 733 744 121 This sig is McQ! :-)
++
Monday, n.:
In Christian countries, the day after the baseball game.
-- Ambrose Bierce, "The Devil's Dictionary"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020209090750.GD32600>