Changed Server Certificate Validation for DoT in dnspyre v2.19.0+? about dnspyre HOT 2 CLOSED

Hello @PeterDaveHello, your observation was precise, the issue was caused by #190, I partially reverted it and released a new fixed version v2.21.1 and the issue you experienced should be fixed, Thanks, please reopen if the issue persists with the new version!

dnspyre --version
2.21.1-darwin-amd64

dnspyre --dot --server="anycast.dns.nextdns.io" google.com
Benchmarking anycast.dns.nextdns.io:853 via tcp-tls with 1 concurrent requests


Total requests:		1
DNS success codes:	1

DNS response codes:
	NOERROR:	1

DNS question types:
	A:	1

Time taken for tests:	 73.79ms
Questions per second:	 13.6
DNS timings, 1 datapoints
	 min:		 71.3ms
	 mean:		 73.4ms
	 [+/-sd]:	 0s
	 max:		 75.5ms
	 p99:		 75.5ms
	 p95:		 75.5ms
	 p90:		 75.5ms
	 p75:		 75.5ms
	 p50:		 75.5ms

from dnspyre.

After reviewing the changelog, I suspect the changes introduced in #190 might be related to the issue I'm experiencing with DoT testing in dnspyre versions 2.19.0 and later.

This change seems to alter how DNS server hostnames are resolved for plain DNS and DoT.

However, I'm not deeply familiar with the intricacies of this project, so it would be beneficial if someone more acquainted with it could confirm or clarify this observation.

from dnspyre.