(Sample) MCSE 2003 DNS Exam Questions and Answers

70-291 level questions

Q:
You manage DNS1, a computer running Windows Server 2003 and the Domain Name System (DNS) Server service. You create the DNS domain corp.com and a subdomain of corp.com named west.corp.com in a zone named corp.com on DNS1. The zone corp.com is the only zone hosted on DNS1. You use the Add New Delegation wizard in the DNS console to delegate authority of west.corp.com to DNS5, a computer running Windows 2000 Server and the DNS server service. In the Properties dialog box for TCP/IP on DNS5, you enter the IP address of DNS5 in the Preferred DNS server field.
What step should you take to enable the DNS Server service on DNS5 to communicate with DNS1?
Configure DNS1 as a forwarder for DNS5.
Configure DNS1 in the root hints of DNS5.
Configure DNS1 as an alternate DNS server for DNS5.
Configure DNS1 as a master name server for DNS5.
A:
You should configure DNS1 as a forwarder for DNS5. A forwarder is a DNS server to which a DNS server forwards queries. For example, if DNS1 is configured as a forwarder for DNS5, and DNS5 receives a query that it cannot answer from its own set of records or the information in the DNS server cache, it forwards the query to DNS1 for resolution. There is no configuration required on a DNS server to make it a forwarder. Instead, the IP address of the computer that is used as a forwarder must be defined on each DNS server that will use the forwarder.
You should not configure DNS1 as a master name server for DNS5 because the servers host separate zones. A master name server is either a primary or a secondary name server for a zone from which a secondary name server can receive zone transfers.
You should not configure DNS1 in the root hints of DNS5, since DNS1 does not host a root zone. On both servers, the root hints should contain information about the name servers that host the root zone on the Internet. This information is loaded by default from the preconfigured file named cache.dns.
You should not configure DNS1 as an alternate server for DNS5. You configure an alternate server to allow the DNS resolver to contact a second server if the resolver cannot contact the primary DNS server. The DNS server service does not use this information to locate an alternate server.

Q:
You manage one of your company's Domain Name System (DNS) servers. The server is a primary server for one forward lookup zone. You want to disable support for round robin.
In the DNS console, what should you use to disable support for round robin?
A: N/A

Q:
You manage DNS1, a computer running Windows Server 2003 and the Domain Name System (DNS) Server service. You create a new zone on DNS1 for the DNS domain corp.com. You also create the subdomain division3.corp.com in this primary zone. You create resource records for both domains.
You use WKS2, a computer running Windows 2000 Professional, to administer the network. WKS2 is configured to use DNS1 as its primary DNS server. When you run the command "nslookup -ls -d division3.corp.com" on WKS2 to obtain information about computers in the child domain, you receive an error indicating that this is a non-existent domain.
What should you do to obtain data about this subdomain with the nslookup command?
In the TCP/IP properties in the Local Area Connection of WKS2, enter division3.corp.com in the "Append these DNS suffixes (in order)" field.
Create a name server (NS) record for DNS1 in division3.corp.com.
Configure DNS1 as a slave server.
Use the "nslookup -ls -d corp.com" command.
A:
You should use the command "nslookup -ls -d corp.com" to obtain information about the computers in division3.corp.com. Since there is not a separate zone for division3.corp.com, the nslookup command cannot return information when queried for division3.corp.com instead of corp.com.
You should not create an NS record for DNS1 in division3.corp.com because this is a subdomain, not a zone. An NS record is associated with a zone, not with a DNS domain name.
NOTE: Syntax might be wrong, in W2K at least there is not dash in front of the ls, nor does it seem to work either way non-interactively...

Q:
How to use NSLOOKUP to see if DNS is returning a result from WINS?
A:
nslookup
set querytype=a (or set querytype=ptr)
host-a.example.microsoft.com. (or 1.0.0.10.in-addr.arpa.)
Normally, when a DNS server answers a query from its authoritative zone data, it uses the set minimum or default TTL for the zone or the record-specific TTL value (if one is configured). In so doing, TTLs are decreased in answers the server returns if based on non-authoritative data, such as a cached record at the server.
WINS lookups present an exceptional case, where an answer received back from a WINS server is cached by the DNS server but is also considered to be authoritative data. In this case, the WINS sourced data is returned to clients as authoritative but ages while in the DNS server names cache, causing the TTL used by the server to decrease over time.

· (1x) DNS primary and alternate MX record simulation I spent a lot of time on and know I got wrong as instead of creating more records it just replaced the last one in the list…

· (6x) DNS zones for resolution performance and WAN link minimization
o (1x) primary v. secondary v. stub
o (2x) conditional forwarders
o (2x) root hints
o (1x) ADI DNS across AD partitions

70-293 level questions

Q/A:
You would configure a client computer with multiple DNS suffixes so that unqualified name resolution requests can be resolved by querying multiple DNS zones.

Q:
You just made zone changes to the DNS server. You go to your client computer, which is running Windows 2000 Professional, and use the nslookup utility to verify that your changes have been applied. When it appears that the changes have not been applied, you return to the DNS server, and find that the changes have indeed been made.

What has probably happened?

The nslookup utility is displaying information that is cached on the DNS server.

The nslookup utility is displaying information that is cached on your client computer.

You have used the wrong utility to verify the changes to the DNS server.

You neglected to restart the DNS server after making the zone changes.

A:
The nslookup utility is probably displaying information that is cached on your client computer rather than the new zone information. To display the current information, you should flush the cache either by using the ipconfig /flushdns command or by stopping and restarting the DNS client service on your computer.