Question Locked

Can you configure Win2K3 DNS to return its own record every time?

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My company has three business groups in three buildings, behind three firewalls, and each has its own Win2K3 forest. The company decided to deploy a shared forest across all three buildings for all three business units to use and established two-way trusts from this forest to the other three forests. The shared forest DCs replicate via IPSec over the Internet and it works well.

The first resource forest DC was deployed successfully in building one, but we started running into dns resolution issues after we deployed to buildings two and three. When we ping the FQDN of the shared forest, the local shared forest DNS server sometimes returns the local DNS/DC's IP address and other times it returns the remote DCs IP address. The problem is that the remote DCs are behind the firewalls of buildings 2 and 3 and not accessible from building 1. This leads to our users not being able to download policies when they login to the shared forest.

Considering that all of our DCs are DNS servers also, we would like to find a way to configure each DNS server to return its own record instead of the remote DCs record when pinged. Is this at all possible?

2 replies

by Former member

To properly configure your forward DNS zone, you first need to create an address record for your mail server. This address record is the forward address entry discussed earlier. To create this record, you need to use the DNS Microsoft Management Console (MMC), if your company self-hosts the DNS zone; otherwise, you should use the tools your ISP provides. The address resource record is represented by an A record. This address record must point to the public IP address where email for the zone should be delivered. This public IP address will probably be your Exchange server?s IP address, and this address must be assigned to you by your ISP. Then, assign the FQDN of that address record to your zone?s MX record. It is possible to use aliases within a DNS zone. Using aliases can minimize the amount of typing required to configure a zone, and it makes possible to provide users with easy-to-remember computer names. The Canonical Name (CNAME) RR specifies both an alias and its target.
http://windowsitpro.com/article/articleid/99556/introduction-to-dns-configuration-for-exchange-admins.html

Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.

This discussion is closed to new replies.