here's more
for PUBLIC services the easy way you can do is just
manipulate your public DNS zone records:
$ORIGIN yourdomain.com
:
:
:
webserver IN 1.2.3.4
www IN CNAME webserver
mailserver1 MX 10 1.2.3.5
mailserver2 MX 20 1.2.3.6
ftp IN 1.2.3.5
this tells the outside world that
your website (www.yourdomain.com, a.ka.
webserver.yourdomain.com) is served by
1.2.3.4..then configure that server accordingly.
all incoming mails would then go to
mailserver1.yourdomain.com (primary) and
mailserver2.yourdomain.com (secondary).
thats 1.2.3.5 and 1.2.3.6. AND
set them up accordingly (mailserver1 should
receive mail for your domain, and mailserver2
should forward mail to mailserver1, etc).
tell your clients to use ftp.yourdomain.com
for ftp uploads..they go to the server
at 1.2.3.5. configure that server for ftp.
this can go on and on such as setting
up news.yourdomain.com, pop.yourdomain.com,
etc...
this is just one simple way that could
help real quick, thru dns.
if you need clustering
or other stuff DNS wont help (other plug
posters can help there).
if you need more DNS config help I can probaly
help out, feel free to email me (though like
i said i have no real world experience except
for my home network of 5-10 pcs).
jondz
[EMAIL PROTECTED]
>
> Hagibis Fan wrote:
>
> >ASCII ART
> >
> >here's one suggestion as to DNS...i'm not sure what
> >you want exactly though, so here's a general layout:
> >
> >
> > DNS SERVER1 DNS2
> > | |
> > ----+----------------------+--
> > FIREWALL
> > --------------------------------
> >| | |
> >| | +----+
> >| | | INTERNAL DNS
> >+-----+----+ |
> >| | | |
> >
> >PC PC PC PC
> >
> > so this is a realy simplified diagram,
> >my point is that you can
> >
> >1. setup your external dns (1 or two of them)
> > visible from the internet..this will serve
> > your domain as well
> >
> >2. your internal LAN can query these DNS
> > directly or they can talk to a local DNS
> > server and that DNS can forward requests
> > to your outside DNS (Or to the internet).
> >
> >Setup local host names also. for example
> >pc1.i.domain.com pc2.i.domain.com, etc...
> >setup your pc's so that their search domain
> >would be i.domain.com first, then domain.com then
> >the internet. point each of this clients
> >to your DNS server (heck put them on the DHCP
> >table that you hand out to the clients).
> >
> >Map out a reverse mapping also for the local
> >hosts so you wont have a problem for services
> >that almost hang without reverse maps (telnet, ftp and
> >such)..fill up the IN-ADDR.ARPA properly for
> >local DNS.
> >
> >
> >dont know yet what to suggest, without knowing
> >yur setup..
> >
> >take this advice with a lot of grain of salt,
> >my only experience is with a home network
> >(about 5-10 hosts).
> >
> >
> Well, Jondz, thanks alot for the ideas.
> At least for DNS setup I can have this as a good guide.
>
> I appreciate it! I'll wait for other ideas with regards to other services...
>
> -Jun
>
>
> --
> Philippine Linux Users' Group (PLUG) Mailing List
> [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph)
> Official Website: http://plug.linux.org.ph
> Searchable Archives: http://marc.free.net.ph
> .
> To leave, go to http://lists.q-linux.com/mailman/listinfo/plug
> .
> Are you a Linux newbie? To join the newbie list, go to
> http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
>
--
Philippine Linux Users' Group (PLUG) Mailing List
[EMAIL PROTECTED] (#PLUG @ irc.free.net.ph)
Official Website: http://plug.linux.org.ph
Searchable Archives: http://marc.free.net.ph
.
To leave, go to http://lists.q-linux.com/mailman/listinfo/plug
.
Are you a Linux newbie? To join the newbie list, go to
http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
