From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: documentation@lists.ipfire.org Subject: Re: DNS forwarding Date: Sun, 04 Aug 2013 12:45:23 +0200 Message-ID: <1375613123.24441.34.camel@rice-oxley.tremer.info> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1603523407985503820==" List-Id: --===============1603523407985503820== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Yes, it basically may be any IP address. A common use case is where you have an internal DNS zone, you need to run your LAN. Microsoft Active Directory does that for example. Of course you wouldn't want your internal zone being public on the Internet - hence this functionality. You may also use external DNS servers to do reverse resolving for your internal LAN and so on. Bascially, it can be any (valid) zone name and any IP address. I hope that clears it up :) -Michael On Sat, 2013-08-03 at 21:45 -0700, Luke Lawry wrote: > @ Erik > > > I edited the description a bit. All I did was add a sentence, fix > some grammar, and rearrange some of the sentences. > > > I do have a question about where it say: > > > "This is intended for private nameservers: if you have a nameserver > on your network which deals with names of the form ....." > > > When I first read this I thought "private" was referring to using a > private IP address but when I saw the picture under "Configuration" it > has a public IP address. Can this forward to a public IP? > > > > > Luke > ----- > > > _______________________________________________ > Documentation mailing list > Documentation(a)lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/documentation --===============1603523407985503820==--