mirror of
https://gitlab.com/shorewall/code.git
synced 2025-01-03 03:59:16 +01:00
Additional tidying of FAQ 2 and Split DNS
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8635 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
3802300d4b
commit
25153aa62b
@ -564,8 +564,10 @@ eth0:66.249.93.111 0.0.0.0/0 206.124.146.176 tcp 993</programlistin
|
||||
gets hacked and you don't have to run a split DNS configuration
|
||||
(separate server or Bind 9 views).</para>
|
||||
|
||||
<para>And before you complain "It's too hard to set up split DNS!",
|
||||
<ulink url="SplitDNS.html"><emphasis role="bold">check
|
||||
<para>If physical limitations make it impractical to segregate your
|
||||
servers on a separate LAN, the next best solution it to use Split DNS.
|
||||
Before you complain "It's too hard to set up split DNS!", <ulink
|
||||
url="SplitDNS.html"><emphasis role="bold">check
|
||||
here</emphasis></ulink>.</para>
|
||||
|
||||
<para>But if you are the type of person who prefers quick and dirty
|
||||
|
@ -38,11 +38,11 @@
|
||||
<title>What is Split DNS</title>
|
||||
|
||||
<para><firstterm>Split DNS</firstterm> is simply a configuration in which
|
||||
the IP address to which a DNS name resolves is dependent on where the
|
||||
client is. It is most often used in a NAT environment to insure that
|
||||
lodcal clients resolve server names to their local RFC 1918 addresses
|
||||
while external clients resolve the same server names to their public
|
||||
counterparts.</para>
|
||||
the IP address to which a DNS name resolves is dependent on the location
|
||||
of the client. It is most often used in a NAT environment to insure that
|
||||
local clients resolve the DNS names of local servers to their RFC 1918
|
||||
addresses while external clients resolve the same server names to their
|
||||
public counterparts.</para>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
|
Loading…
Reference in New Issue
Block a user