extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-01-03 03:59:16 +01:00
Code Issues Packages Projects Releases Wiki Activity

Additional tidying of FAQ 2 and Split DNS

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8635 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2008-07-14 13:07:05 +00:00
parent 3802300d4b
commit 25153aa62b
2 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/FAQ.xml
View File

@ -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 gets hacked and you don't have to run a split DNS configuration
(separate server or Bind 9 views).</para> (separate server or Bind 9 views).</para>
<para>And before you complain "It's too hard to set up split DNS!", <para>If physical limitations make it impractical to segregate your
<ulink url="SplitDNS.html"><emphasis role="bold">check 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> here</emphasis></ulink>.</para>
<para>But if you are the type of person who prefers quick and dirty <para>But if you are the type of person who prefers quick and dirty

10
docs/SplitDNS.xml
View File

@ -38,11 +38,11 @@
<title>What is Split DNS</title> <title>What is Split DNS</title>
<para><firstterm>Split DNS</firstterm> is simply a configuration in which <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 the IP address to which a DNS name resolves is dependent on the location
client is. It is most often used in a NAT environment to insure that of the client. It is most often used in a NAT environment to insure that
lodcal clients resolve server names to their local RFC 1918 addresses local clients resolve the DNS names of local servers to their RFC 1918
while external clients resolve the same server names to their public addresses while external clients resolve the same server names to their
counterparts.</para> public counterparts.</para>
</section> </section>
<section> <section>