All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven M Campbell <Netfilter@SCampbell.net>
Cc: Netfilter ML <netfilter@lists.netfilter.org>
Subject: Re: dnatting
Date: Wed, 13 Jul 2005 10:50:08 -0400	[thread overview]
Message-ID: <42D52A20.3090709@SCampbell.net> (raw)
In-Reply-To: <57F9959B46E0FA4D8BA88AEDFBE58290742E@pxtbenexd01.pxt.primeexalia.com>

Gary W. Smith wrote:
>I agree with everything that has been said BUT I must also interject.  A
>lot small business and many home users who get one or two IP's usually
>don't have a second DNS floating around.  For larger organizations I
>would definitely use the split DNS.  We do that at a couple locations
>when we can.
>  
Split DNS can be implemented on a single DNS server, check your DNS 
servers manual.  The basics are that you create views of your domain 
structure based on the ip address of the requester, if they are inside 
(for instance 10.0.0.0/8) you give them the inside answers, otherwise 
you give them the outside answers.   You should not need multiple DNS 
servers although you should have multiple servers for other reasons. 

>As for this case, I think it's completely acceptable.  
>
>Since this does indeed work I think it should be documented as a viable
>solution (which I think it's in the fine print on one of the docs that I
>read before).
>
>  
FWIW from me I would not accept the answer 'it works so it must be 
okay', that's been the downfall of soooo very many computer projects I 
cannot even begin to count them (a particularily bad attitude for 
programmers).    We'll certainly not argue (and we aren't), it's your 
network and your rules.  My advice is use split DNS from the experience 
that I used to do the sort of thing that you are doing here and I found 
out that it was a bad idea and only created trouble later and I don't 
like trouble, especially if it can be pinned on me!



  parent reply	other threads:[~2005-07-13 14:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 23:19 dnatting Gary W. Smith
2005-07-13 10:39 ` dnatting Jan Engelhardt
2005-07-13 21:19   ` dnatting R. DuFresne
2005-07-13 14:50 ` Steven M Campbell [this message]
2005-07-13 16:33   ` dnatting Donald Murray
2005-07-13 16:39     ` dnatting Steven M Campbell
  -- strict thread matches above, loose matches on Subject: below --
2005-07-13 16:28 dnatting Gary W. Smith
2005-07-13 16:40 ` dnatting Steven M Campbell
2005-07-12 14:05 dnatting Gary W. Smith
2005-07-11 19:09 dnatting Gary W. Smith
2005-07-12  7:34 ` dnatting Payal Rathod
2005-07-12 11:59   ` dnatting Jason Opperisano
2005-07-12 12:50     ` dnatting Payal Rathod
2005-07-12 21:03       ` dnatting Steven M Campbell
2005-07-11 15:18 dnatting Payal Rathod
2005-07-11 15:20 ` dnatting Jan Engelhardt
2005-07-11 18:21   ` dnatting Payal Rathod
2005-07-11 18:38   ` dnatting /dev/rob0
2005-07-11 18:42     ` dnatting Jan Engelhardt
2005-07-11 15:24 ` dnatting Scott
2005-07-11 18:45 ` dnatting Jason Opperisano
2005-07-11 18:54   ` dnatting Jan Engelhardt
2005-07-13  3:21   ` dnatting Donald Murray
2005-07-13  4:48     ` dnatting Jason Opperisano
2005-07-14 15:42 ` dnatting curby .
2005-07-14 15:49   ` dnatting curby .

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=42D52A20.3090709@SCampbell.net \
    --to=netfilter@scampbell.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.