Regarding the following, written by "martin f krafft" on 2024-04-30 at 07:26
Uhr +0200:
# unbound-control list_forwards
. IN forward fc00:39:39::1 192.168.39.1
Sorry, this was done in a different network (I've been debugging
this for days while roaming/working), and the answer corresponding
Hey there,
I am trying to run Unbound 1.19.2 on my Debian laptop because I want
the ability to inject DNS data using `zone-data` as well as
`stub-zone`/`forward-zone` e.g. when I have certain VPN connections
open.
But I am constantly running up against walls:
```
% dig @127.0.0.1 a
Hello,
I am a bit baffled by the following problem. Running unbound 1.4.17
on a Debian machine, at irregular but frequent intervals, the
nameservers for madduck.net will be marked "lame". As a result,
names under madduck.net cannot be resolved.
At the same time, running dig +dnssec gives the
also sprach Ralph Dolmans via Unbound-users
[2015-12-24 00:33 +1300]:
> Are you sure the tcpdump output corresponds to this part of the log?
> The log indicates that no query is send out because the only suitable
> delegation point (the forwarding server) is marked as
Hi Paul,
thanks for your time responding. I'll answer inline:
> Did your forwarder perhaps not answer (in time) ?
They did; the answer was instantaneous, and also tcpdump showed the
response to have arrived within milliseconds.
> Maybe try setting cache-max-negative-ttl: to something like 5
Hi,
I am running unbound (1.5.7 on Debian unstable) on a laptop as
a recursive resolver for localhost and a number of test VMs running
on the machine. I am aware that others use dnsmasq for this, but
I don't particularly like this monolithic do-everything tool and am
rather familiar with unbound