Bind Caching Nameserver <was: Re: Caching nameserver--Name Services Cache Daemon (nscd)>

[feizhou at graffiti.net (Feizhou)]

Les Mikesell wrote:
> On Wed, 2005-08-10 at 13:05, Feizhou wrote:
> 
> 
>>With djbdns, you can just install and run walldns and 
>>forward/split-horizon queries for 0.168.192.in-addra.arpa to the walldns 
>>instance if you don't need names. or you install tinydns if you want names.
> 
> 
> I have no idea what any of that means.  It doesn't sound easier
> than using the stock packages which also 'just work' when you
> add the names and addresses that no other server knows.  It does
> help to have a tool to build the reverse zones for you but webmin
> is probably the way to go if you don't want to do it by hand.
> 

If you just look at walldns it will tell you that it automatically maps 
things like 192.168.0.1 <-> 1.0.168.192.in-addr.arpa

If you want real names, then you have to use tinydns where you can 
create the records.

For an authoritative server, it is probably better running bind since it 
keeps stuff in memory while tinydns hits a cdb (disk i/o). dnscache is 
the only choice if you need a high performance dns cache where bind does 
not meet what is required.

For config file format, tinydns beats bind hands down. Anyway, for small 
zones, bind is probably less effort since it comes with CentOS.