Description of problem:

When not using the "-t" flag it is assumed the user only cares about A, AAAA and MX resource records. If the user queries a name which is linked to another type of record, but not these "default" records there is no NXDOMAIN message, which can be confusing.

For example, if the name "2.0.168.192.in-addr.arpa" is associated with a PTR record and has no A, AAAA or MX records, there will be no output:

=====
[root@rhel82 ~]# host -t ANY 2.0.168.192.in-addr.arpa
2.0.168.192.in-addr.arpa domain name pointer foo.example.lab.com.
[root@rhel82 ~]# host 2.0.168.192.in-addr.arpa
[root@rhel82 ~]# 
=====

But if we query a name which has no records at all we get the expected NXDOMAIN response:

=====
[root@rhel82 ~]# host -t ANY 1.0.168.192.in-addr.arpa
Host 1.0.168.192.in-addr.arpa not found: 3(NXDOMAIN)
[root@rhel82 ~]# host 1.0.168.192.in-addr.arpa
Host 1.0.168.192.in-addr.arpa not found: 3(NXDOMAIN)
=====

Version-Release number of selected component (if applicable): bind-utils-9.11.13-5.el8_2.x86_64


How reproducible: always


Steps to Reproduce:
1. Configure a zone with a single PTR record:

=====
[root@rhel82 ~]# tail -n7 /etc/named.conf 
zone "0.168.192.in-addr.arpa" IN {
	type master;
	file "0.168.192.in-addr.arpa.hosts";
};

include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";
[root@rhel82 ~]# cat /var/named/0.168.192.in-addr.arpa.hosts 
$TTL 86400
@     IN   SOA lab.com. root.lab.com. (  
              2020062401 ; Serial  
                    3600 ; Refresh  
                     900 ; Retry  
                  604800 ; Expire  
                    3600 )  ; Minimum  
     IN      NS         rhel82.lab.com.  
2    IN      PTR        foo.example.lab.com.
=====

2. Restart named

3. Perform a query using "host" without specifying the "-t" flag (implies we only care about A, AAAA and MX records). Make sure to query a name that is associated with another type of record (i.e., not A, AAAA or MX).

Actual results:

We get no output.

=====
[root@rhel82 ~]# host -t ANY 2.0.168.192.in-addr.arpa
2.0.168.192.in-addr.arpa domain name pointer foo.example.lab.com.
[root@rhel82 ~]# host 2.0.168.192.in-addr.arpa
[root@rhel82 ~]# 
=====

Expected results:

We get a NXDOMAIN response

Additional info:

I am not sure if this is any different upstream, but I'm assuming it isn't.