"When a user enters an FQDN, the resolver queries DNS using that name.
Likewise, when a user enters a multiple-label, unqualified (not terminated
with a period) name, the DNS resolver adds a terminating period and queries
DNS using that name."
(
http://www.microsoft.com/technet/pro....mspx?mfr=true)
WindowsXP SP2. Domain members. Win2003 DNS server. Domain name is
mydomain.com.
Name resolution works fine.
I'm add a host (A) record to the mydomain.com DNS zone with the asterisk as
hostname:
* IN A 192.168.0.1
And all client computers (domain members) will never try to add a
terminating period when a user enters a multiple-label name.
Instead, resolver always add a primary dns suffix to multi-label names. And
> nslookup anyInternetDomain.com
Server: mydns.mydomain.com
Address: x.x.x.x
Name: anyInternetDomain.com.mydomain.com
Addresses: 192.168.0.1
Why client computers will never try to add a terminating period when a user
enters a multiple-label name in that case? Resolver's bug?