Comment 4 for bug 1305156

OK, in first instance I thought you were talking about djbdns whereas I should have noticed that you gave package details for dbndns. Sorry about the mistake.

AIUI dbndns is a fork of djbdns, so I will assume that it is similar to djbdns in the respects relevant here. Under that assumption I revise my earlier prescription to read as follows.

The dnscache daemon should listen at IP address 127.0.0.1 in order to provide DNS name service to the local machine
and the dnscache daemon or the script that starts it should register this address with resolvconf by means of something equivalent to `echo "nameserver 127.0.0.1" | resolvconf -a lo.dnscache` after it starts
and should de-register this address before the daemon stops by means of something equivalent to `resolvconf -d lo.dnscache`
and dnscache's resolvconf update script /etc/resolvconf/update.d/dnscache should ignore this address when compiling the list of addresses to which dnscache should forward.

My second error was to think that the djbdns package already supported resolvconf but now I realize that resolvconf support has never been added to djbdns. So the prescription I just gave is a description of what still needs to be done to make djbdns or dbndns work with resolvconf. The resolvconf package includes /etc/resolvconf/update.d/dnscache but (1) this script is not well maintained and (2) it should really be in one of the djbdns/dbndns packages, possibly dnscache-run.

Please see my comment[0] in Debian bug report 582755 for background.

[0]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582755#46

Conclusion: Djbdns and dbndns integration with resolvconf is incomplete. The correct solution is to complete the integration. Would you like to help with this?