A few members of my team are trying to address a use case where a user can type in the short name of server such as host1 and have it properly resolve to the FQDN/IP. They do not want to use domain suffix at the client side. Here is what they are trying to do exactly ---
ping host1 and get the IP address back as it is listed in lab.domain.com
host1.lab.domain.com exist in a zone on the DNS server and there is another primary zone of domain.com as well.
The client host has a FQDN of client.domain.com and the client uses the DNS server that is authorative for domain.com as well as lab.domain.com.
host1 lives in the lab.domain.com zone only. Without using domain suffix at the client side, it would stand to reason to me that if the client where to try ping host1 from the command line that they would not get resolution. If they used just domain.com as the suffix still nothing and finally if they included domain suffix lab.domain.com they would get a resolution.
My teammates believe they can achieve the level of functionality by eliminating domain suffix on the NIC and then using stubzones or secondary zones - their efforts have been unsuccessful. I personally think they cannot get this done using those methods and would instead have to use suffix at the client side -- unless they wanted to hack BIND --- which is not what we are using. This is a Windows DNS environment.
Can anyone offer any correction to my thinking and a possible resolution to provide the level of functionality desired.