Case Project 11-1 Configuring Zones You have an active directory forest named cs

Question

Case Project 11-1 Configuring Zones You have an active directory forest named csmtech.local and two active directory domains in the forest named csmpub.local and csmsales.local. You want the DNS servers in each domain to be able to handle DNS queries from client computers for any of the other domains. DNS servers in the csmtech.local and csmpub.local domains should be authoritative for their own domains and csmsales.local domain. However, DNS servers in csmsales.local should be authoritative only for csmsales.local How should you set up the DNS servers and zones to handle this situation? Explain how the DNS servers in each domain should configured with zones. Be sure to include information about replication scope and zone types

Explanation / Answer

There's usually two scenarios people want to cater for:

Scenario 1

If someone living in one of your domains - let's say a.local, wants to resolve something in b.local, such as www.b.local, then the easiest way to make this happen is to create something called a conditional forwarder on your DNS servers in a.local.

I'm not sure what operating system you're using, but I'll assume it's Server 2008 R2. If you open the DNS Management console, you can:

This is how you add a forwarder for another domain to your domain. Of course, there's a little more to it than that. You will need to talk to the DNS administrators from b.local and ask them to allow zone transfers to your DNS server's IP. The same is true in reverse if they want to resolve names from a.local.

Scenario 2

If someone in a.local wants to resolve a flat name in another domain or forest, then you need to specify something called a DNS suffix search list for your clients in a.local. There are a few ways to do this, two of the most popular of which would be:

The DNS suffix search list would typically have the user's domain first in the list, and then any other domains that should be automatically searched after that. For example:

What happens is the user in a.local might type appServer into a web browser, in which case using the previous example, the the user's computer would first look for appServer.a.local, then appServer.b.local, appServer.c.local, and so on until it found a matching server. Of course, once it finds a match it stops looking, so if appServer lived in a.local, it wouldn't need to search in b.local, c.local etc.

If you enable both DNS conditional forwarding and a domain suffix search order, you will cover most of your user's requirements. There are some legacy scenarios as well, such as NetBIOS and so on, but I wouldn't want to confuse you with too much information if this is all new to you.

Some articles you can read are:

Cheers,
Lain

Related Questions

Navigate

• Browse (All)
• Browse C
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.