> So if I understand correctly, the right thing to do would be
> to add the dnscache address to /etc/resolvconf/resolv.conf.d/base
> and *not* include the dnscache address under dns-nameservers in
> /etc/network/interfaces.
That will work, but only because there's a bug in
/etc/resolvconf/update.d
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 revis
** Description changed:
- I have a forwardonly dnscache (from dbdns) set up on my system, with a
+ I have a forwardonly dnscache (from dbndns) set up on my system, with a
forwarding address set up to our campus resolver.
My system has a static IP configuration and in my
/etc/network/inter
Thanks for the quick reply! dbndnscache doesn't come with an init script
AFAICT. I also did not see any code in the update.d/dnscache to ignore
existing dnscache addresses, but I may have missed it
So if I understand correctly, the right thing to do would be to add the
dnscache address to /etc/res
Probably not a bug, but if there turns out to be a bug then it is in the
djbdns package.
** Package changed: resolvconf (Ubuntu) => djbdns (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/130515
Dnscache should listen on 127.0.0.1
and the dnscache initscript should register this address with resolvconf
and dnscache's resolvconf update script should ignore this address when
compiling the list of addresses to which dnscache should forward.
So far as I know this is already the case. Please
