Bug#374928: multiple servers do make sense

captain toro commander1oldsmobile at yahoo.com
Fri Oct 20 19:52:55 CEST 2006


Greetings-

There has been some mention of using pdnsd with bind or other dns servers:

> BTW, does it make sense to have 2 name servers running in parallel ?

1. pdnsd is actually made to work with bind for example and maybe others
2. pdnsd can be used to cache recent lookups from bind
3. bind can be run as an external nameserver to the WAN from a static IP with 
the pdnsd just used to service the local machine from cache for example
4. bind can be run as an internal nameserver just to the LAN with the pdnsd
just used for a cache
5. pdnsd can lookup addresses from a local bind the same as any nameserver
on the LAN or ISP or root nameservers
6. pdnsd is very fast compared to bind when repetative authoritative lookups
are unneeded or just for surfing
7. absolutely, running bind and pdnsd in parallel makes a lot of sense here

These are only a few examples. The pdnsd was originally written to work with
or without an instance of bind or named running on the same machine.

I have been using bind on 127.0.0.1:53 with pdnsd running on 127.0.0.2:53 and
then pointing to 127.0.0.2 in /etc/resolv.conf with good results. They do not
conflict. The pdnsd is certainly intended to work along with bind as mentioned
in the documentation.

Trying to make pdnsd conflict with bind or any other nameserver package is 
A VERY BAD FIX. 

Please don't force pdnsd to remove bind or vice-versa.

-Captain









More information about the pkg-java-maintainers mailing list