diff --git a/docs/FAQ.xml b/docs/FAQ.xml index a2d726dd6..c9e969592 100644 --- a/docs/FAQ.xml +++ b/docs/FAQ.xml @@ -564,8 +564,10 @@ eth0:66.249.93.111 0.0.0.0/0 206.124.146.176 tcp 993 - And before you complain "It's too hard to set up split DNS!", - check + 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!", check here. But if you are the type of person who prefers quick and dirty diff --git a/docs/SplitDNS.xml b/docs/SplitDNS.xml index d3d8803a7..bb425cdf9 100644 --- a/docs/SplitDNS.xml +++ b/docs/SplitDNS.xml @@ -38,11 +38,11 @@ What is Split DNS Split DNS 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. + 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.