Microsoft windows 2000 DNS Unqualified Single-Label Query Scenarios, Name Resolution Scenarios

•The response is returned to the client.

Name Resolution Scenarios

This section provides name resolution scenarios for a multi-homed machine using unqualified single-label and fully qualified queries. In this scenario the Global suffix search list is not specified.

The following table displays the machine’s DNS configuration:

CONFIGURATION PARAMETER		VALUE
Primary DNS Name		mydomain.microsoft.com.
		(default–same as domain
		membership)
Ethernet0	DNS Servers	e1, e2, e3 (from DHCP)
(preferred)	DNS Domain Name	dns.microsoft.com. (from
		DHCP)
TokenRing0	DNS Servers	t1, t2, t3 (from DHCP)
	DNS Domain Name	dns.ntlab.microsoft.com.
		(from DHCP)

The Unqualified Single-Label Query Scenarios

Lookup a name on the Ethernet segment: ping ntserver

•Query e1 for ntserver.mydomain.microsoft.com.

•Positive response

Lookup a name on the Token Ring segment: ping products1

•Query e1 for products1.mydomain.microsoft.com.

•Negative response

•Query t1 for ‘products1.mydomain.microsoft.com.’

•Positive response

Lookup a name on the Corporation’s Intranet: ping thunder

•Query e1 for thunder.mydomain.microsoft.com.

•Negative response

•Query t1 for thunder.mydomain.microsoft.com.

•Negative response

•Query e1 for thunder.dns.microsoft.com.

•Positive response

Lookup a bogus name: ping boguz

•query e1 for boguz.mydomain.microsoft.com.

•negative response

•query t1 for boguz.mydomain.microsoft.com.

•negative response

•query e1 for boguz.dns.microsoft.com.

Windows 2000 White Paper 40