Am 05.02.2018 um 15:12 schrieb Jan Komissar (jkomissa):
> Hi Alex,
>
>
>
> I don’t think stub-host supports @, only stub-addr does.
What works for me with @port also is stub-addr resp. forward-addr.
Sorry. I read sloppyly. jo
Am 04.02.2018 um 15:47 schrieb Alex Simenduev via Unbound-users:
> Adding @port-number doesn't work like for "forward-addrs/stub-addr". Is
> there any way?
Works for me.
Unbound version? Platform? Full config stanza?
Error message? Symptoms?
jo.
Am 09.01.2018 um 19:53 schrieb Dave Warren via Unbound-users:
> That's... Ugly. Effective though, and appreciated!
>
> I was hoping for something that could work at the domain level rather
> than at the individual host level, but it appears only BIND offers this
> and I don't intend to switch
Am 30.11.2016 um 17:41 schrieb Tim Smith via Unbound-users:
> Interesting idea, nice bit of thinking outside the box ! But in
> relation to "should be alright after cache data times out" , does
> that mean that the idea might not work too well if I've got "prefetch:
> yes" in my config ?
In
Am 30.11.2016 um 15:25 schrieb Tim Smith via Unbound-users:
> Hi Ralph,
>
> Hmm... bad news ...have just looked into it and OpenBSD default config is :
> remote-control:
> control-enable: yes
> control-use-cert: no
> control-interface: /var/run/unbound.sock
>
>
> So
Hello,
If this is a double post, I'm sorry. I just have no way of checking if
this request arrived at the list (I didn't get a copy, that much I
know). Maybe if someone could at least confirm that it arrived?
Here the original text:
Lately I started implementing dnssec, which starts to work
This time I got a copy. No need to confirm. (Don't know what happened
before.) jo.
