Is it necessary to block HTTPS records for the Plugin Block Unqualified?

[msoxzw]

Currently, the Plugin Block Unqualified blocks A and AAAA records:

dnscrypt-proxy/dnscrypt-proxy/plugin_block_unqualified.go

Lines 34 to 36 in 8e46f44

	if question.Qclass != dns.ClassINET || (question.Qtype != dns.TypeA && question.Qtype != dns.TypeAAAA) {
	return nil
	}

As more and more browsers and operating systems request HTTPS records, should the Plugin Block Unqualified also block this record type?

[lifenjoiner]

That doesn't block HTTPS records, try:

dig -t https www.cloudflare.com

Unqualified means:

dnscrypt-proxy/dnscrypt-proxy/example-dnscrypt-proxy.toml

Lines 320 to 322 in 8e46f44

	## Immediately respond to A and AAAA queries for host names without a domain name
	block_unqualified = true

For example: "cloudflare" without ".com" which is not a legal internet domain name, and those random strings Chrome used to query in the past.

Append:
dig -t https cloudflare will bypass this.
Maybe we can expand the types to be tested, when HTTPS record percentage reaches some value.

[msoxzw]

Sorry for ambiguity in my issue.

Append:
dig -t https cloudflare will bypass this.
Maybe we can expand the types to be tested, when HTTPS record percentage reaches some value.

It is exactly what I would like to say.