From: "Linux" <linux@usermail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Forward all traffic to another Public address
Date: Sun, 8 Dec 2002 17:27:18 -0700 [thread overview]
Message-ID: <005f01c29f19$bf988dc0$b22826d8@bfons> (raw)
In-Reply-To: 1039368044.9597.9.camel@localhost.localdomain
Actually,
I will be making the DNS change and only want all traffic to forward while
propagation takes place. Would propagation be any faster if I lower the
TTL? If so, this would make it a non-issue.
Linux303
----- Original Message -----
From: "Ben Russo" <ben@umialumni.com>
To: "Linux" <linux@usermail.com>
Sent: Sunday, December 08, 2002 10:20 AM
Subject: Re: Forward all traffic to another Public address
> I don't know about the iptables,
> But one thing I can tell you from experience setting up LOTS of servers
> in data centers is to make complex use of DNS.
> 1. When setting up a server give it a canonical name that relates to
> the server and it's location.
> 2. Assign seperate CNAME's for the services, even sometimes multiple
> CNAME's for the same service. For example "us-popmail.myservers.net"
> "eu-popmail.myservers.net" "webmail.myservers.net" "www.myservers.net"
> etc.
> 3. Then you might have all of these DNS entries referring to the same
> box at first. But later, if you evern need (for scalability or for
> distribution or for redundancy) to have more than one machine, your
> users/clients software won't need to be reconfigured, you can instead
> just change DNS and the clients won't be the wiser.
>
> So, with regards to the stuff below you should change DNS MX and A
> records appropriately, IP redirection isn't the right way to do this.
>
> On Sat, 2002-12-07 at 12:15, Linux wrote:
> > Does anyone have any imput on this? Also, would iptables be the best
> > way to redirect the traffic? I don't have access to the router.
> >
> > Linux
> > ----- Original Message -----
> > From: Linux
> > To: netfilter@lists.netfilter.org
> > Sent: Tuesday, December 03, 2002 2:52 PM
> > Subject: Forward all traffic to another Public address
> >
> > Hello All,
> >
> > I am freaking going crazy and pulling my hair out. Here is I
> > want to do.
> > Forward all traffic (smtp, pop3, web,etc) for one IP address
> > in Server box located in CA to a Server in TX
> > These boxes are on separate networks.
> > Here is what I did
> >
> > iptables -t nat -A PREROUTING -s 216.x.x.x -d 238.x.x.x -m
> > state --state RELATED,ESTABLISHED -j MASQ
> > iptables -t nat -A PREROUTING -d 238.x.x.x -j DNAT --to
> > 216.x.x.x
> >
> >
> > Can someone please help me as I cannot figure out what I am
> > doing wrong.
> >
> >
> > Thank you,
> >
> > Linux
> --
> Ben Russo <ben@umialumni.com>
>
prev parent reply other threads:[~2002-12-09 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 21:52 Forward all traffic to another Public address Linux
2002-12-07 17:15 ` Linux
[not found] ` <1039368044.9597.9.camel@localhost.localdomain>
2002-12-09 0:27 ` Linux [this message]
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='005f01c29f19$bf988dc0$b22826d8@bfons' \
--to=linux@usermail.com \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.