[prev in list] [next in list] [prev in thread] [next in thread] 

List:       djbdns
Subject:    Re: tinydns and dnscache on the same server (was: tinydns, dnscache confusion issue)
From:       Peter van Dijk <peter () dataloss ! nl>
Date:       2001-12-31 19:22:16
[Download RAW message or body]

On Mon, Dec 31, 2001 at 06:03:27PM +0100, Laurent G. Bercot wrote:
[snip]
>  The solution I see is : use IP aliasing on all your internal network.
> Make all your machines have 2 IPs : one public (their current IP
> address), and one private, 192.168.something. Tell your machines to
> use the public IPs by default. Then, if you attributed 192.168.0.1
> to your server, run dnscache on 192.168.0.1. Be careful to put your
> server's public IP in env/IPSEND. And put 192.168.0.1 in your
> clients' /etc/resolv.conf or the like.
>  That way, your network should be able to access your dnscache,
> while the external world should not.

It's even easier. As long as the gateway you configured your clients
to use knows how to find the special IP assigned to your dnscache,
everything is good. No need for double IPs on *all* boxes there.

Greetz, Peter
-- 
huk ~ kek
[prev in list] [next in list] [prev in thread] [next in thread]