Hi Raymond,
On 03/05/18 22:43, Raymond Bannan via Unbound-users wrote:
> I've spent several hours trying various permutations of the following
> config, but no matter what I do I can't get unbound to forward a DNS
> request over TLS:
This config looks correct. It should be connecting with TLS.
I've spent several hours trying various permutations of the following
config, but no matter what I do I can't get unbound to forward a DNS
request over TLS:
server:
tls-cert-bundle: "C:\Program Files\Unbound\cabundle.crt"
forward-zone:
name: "."
forward-ssl-upstream: yes
forward
Im having the same issue here with my servers. several queries fails when
using my server's source IP but, Google public DNS return an answer.
my workaround was to forward those queries to 8.8.8.8 using forward domain.
i wonder if there's a way to find what's causing those SERVFAIL.
--
Respect
We run a robust carrier-grade e-mail service in the cloud and have a
dedicated DNS infrastructure that has undergone extensive tuning to work in
AWS, see
https://www.sparkpost.com/blog/undocumented-limit-dns-aws/
https://www.sparkpost.com/blog/dns-aws-network-lessons/
https://www.usenix.org/s
Hi,
Unbound 1.7.1 is available for download:
https://www.unbound.net/downloads/unbound-1.7.1.tar.gz
sha256 56e085ef582c5372a20207de179d0edb4e541e59f87be7d4ee1d00d12008628d
pgp https://www.unbound.net/downloads/unbound-1.7.1.tar.gz.asc
Note: The NLnet Labs website has been updated, and now integra