hanvinke

Now finally getting an answer with stubby 0.3.0: ; DiG 9.17.1 dig @127.0.0.1 pir.org ;; global options: +cmd ;; Got answer: ;; ->>HEADERHEADER

@triatic Ah, thanks missed the ad flag. There are also just atomic files downloaded and no root.key either. Next time I take a better look. Thank you for correcting me....

Default location for root trust anchor should be in %appdata%\GETDNS directory. But stubby -i shows otherwise: "default_trust_anchor_location": , Unfortunately the full path is not readable., it is truncated. Changing the...

Had this too. There was a leftover .so from getdns which I removed and then rebuilded. Stubby 0.3.0 and getDNS 1.6.0 worked after that.

``` ARCH-PC% stubby -i [05:55:36.353545] STUBBY: Stubby version: Stubby 0.3.0 [05:55:36.354122] STUBBY: Read config from file /etc/stubby/stubby.yml { "all_context": { "add_warning_for_bad_dns": GETDNS_EXTENSION_FALSE, "appdata_dir": , "append_name": GETDNS_APPEND_NAME_TO_SINGLE_LABEL_FIRST, "dns_transport_list": [ GETDNS_TRANSPORT_TLS ],...

Sorry, will put that in a txt file above. Maybe you are right about the cause. Might be it is in the building options. I can see that I also...

I see that I probably use gnuTLS, I thought I left that out when building. Will build again later, sorry!

I have rebuild with openSSL and also do not have errors. ● stubby.service - stubby DNS resolver Loaded: loaded (/usr/lib/systemd/system/stubby.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2020-05-13...

However: very convenient (re)building! 

@ArchangeGabriel @rampageX Did you figure out the problem of the error? TLSv1.3 does not support cipher suites from previous TLS protocol versions. Maybe you added 'tls_cipher_list' to your build?