All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Need to solve a NAT problem, any takers.
Date: Fri, 12 Jan 2007 23:45:17 -0600	[thread overview]
Message-ID: <45A871ED.9070500@riverviewtech.net> (raw)
In-Reply-To: <57F9959B46E0FA4D8BA88AEDFBE5829024EF8A@pxtbenexd01.pxt.primeexalia.com>

On 01/11/07 21:35, Gary W. Smith wrote:
> Internally our DNS server are split giving us internal IP's when queried
> internally and external's when queried externally.  This works fine.
> Our second DNS server internally slaves the primary.  Because we are
> using this split functionality when it slaves the internal IP's it gets
> the internal IP configuration.  Works great.  But in order to replicate
> the external range it must do so by replicating from the external IP.
> This fails at the IP's is NAT'd in by port only.  Years ago we solved
> this by running a second POSTROUTING rule and an OUTPUT rule on the
> firewall.  When I load these rules now 

I know this is not an IPTables / NAT answer, but I think it may possibly 
be an answer to your need.  What if you add a different subnet to your 
two DNS servers that each of them consider to be for the external view. 
  Tell your secondary to contact the primary on it's IP in this external 
view subnet.

Just a thought.



Grant. . . .


  parent reply	other threads:[~2007-01-13  5:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12  3:35 Need to solve a NAT problem, any takers Gary W. Smith
2007-01-12 15:45 ` Pascal Hambourg
2007-01-12 17:03   ` Gary W. Smith
2007-01-13  5:45 ` Grant Taylor [this message]
2007-01-13  8:17   ` Gary W. Smith

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=45A871ED.9070500@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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.