Closed DaddyMadu closed 1 year ago
I believe there is a confusion for the insecure-domain configuration option. The insecure part refers to DNSSEC and not the trust of TLS certificates. That means that Unbound treats the www.example.com
zone as DNSSEC-insecure.
As for the issue you report I am not exactly certain what you are trying to achieve :).
Closing this as inactive non-issue.
dear team good day i have 3 domains on the same server and all included in one multi domain positive comodo ssl and the server has one static ip domain insecure future is not excluding connection to main domain and tls is connected to both domains To reproduce 1- setup up a domain and sub domain like www.example.com, dns.example.com 2- install multi domain ssl : www.example.com, dns.example.com 3- setup unbound DOT server with tls certificate on port 853
add insecure domain parameter and define www.example.com as insecure
Expected behavior
query dns over tls on www.example.com unbound still accepts connection from this domain as it's already included in the certificate chain i should only be able to connect to dns.example.com or maybe i got it wrong and shouldn't labeled this as bug! please feel free to correct me, thank you!
System: - Unbound version: 1.13.1 - OS: ubuntu 21.10 -
unbound -V
output: