Exxhange SQL And IIS- P82 doc

382 Chapter 7 • Managing the Edge Transport Server 6. Click Ye s to reboot the server so that the changes take effect. Enabling Name Resolution Lookups between the Edge Transport and Hub Transport Servers Suffi x It’s important that the edge transport server and any hub transport servers in your Exchange 2007 organization are able to see each other using name resolution. To accomplish this goal, you can create the necessary host record in a forward lookup zone on the internal DNS server used by the edge transport and hub transport servers. Figure 7.3 The DNS Suffi x and NetBIOS Computer Name NOTE Since any Exchange 2007 hub transport server in your Exchange organization needs to be added to the Active Directory, before you can install this role only the host name of the edge transport server needs to be manually added to the respective forward lookup zone. Managing the Edge Transport Server • Chapter 7 383 You do so by performing the following steps: 1. Log onto the internal DNS server used by the edge transport and hub transport servers. 2. Click Start | Administrative Tools and then click DNS. 3. In the DNS Management snap-in, expand the Server node and then Forward Lookup Zones (see Figure 7.4). 4. Now right-click the respective Forward Lookup Zone and select New Host (A) in the context menu. 5. Enter the hostname and IP address of the edge transport server and click Add Host (see Figure 7.5). Figure 7.4 DNS Management MMC Snap-in 384 Chapter 7 • Managing the Edge Transport Server 6. Close the DNS Management snap-in and log off the internal DNS server. You may also choose to simply add the hostname and IP address of the edge transport server to the local hosts fi le on each hub transport server, and the hostname and IP address of any hub transport server to the local hosts fi le on the edge transport server in your Exchange organization. Although this is a perfectly supported solution, we don’t recommend you use it unless you’re dealing with a small shop that has maybe one edge transport server and one or perhaps two hub transport servers. If you’re a messaging administrator/consultant in a large Exchange organization that contains multiple edge transport servers as well as several hub transport servers, it’s far better to keep the name resolution centralized on an internal DNS server. You add the hostname and IP address to the local hosts fi le on the server by performing the following steps: 1. Log onto the edge transport or hub transport server. 2. Click Start | Run and type C:\windows\system32\drivers\etc and press Enter. 3. Now open the hosts fi le in Notepad. 4. Type the IP address and hostname of the server (see Figure 7.6). Figure 7.5 Creating a New Host (A) Record Managing the Edge Transport Server • Chapter 7 385 Figure 7.6 Entering the IP Address in the Hosts File Figure 7.7 Purging and Preloading NBT Remote Cache Name Table 5. Save the changes and close Notepad. 6. Now open a Command Prompt Window by clicking Start | Run and then typing CMD.EXE. 7. You now need to purge and reload the remote cache name table, which is done by typing NBTSTAT –R followed by pressing Enter (see Figure 7.7). 386 Chapter 7 • Managing the Edge Transport Server 8. Verify that you can ping the respective servers using the fully qualifi ed domain name, and make sure it’s the correct IP address that’s resolved (see Figure 7.8). NOTE You need to perform Steps 1 through 8 on each edge transport and hub transport server in your Exchange organization. Figure 7.8 Pinging the Edge Transport Server Confi guring DNS Settings If you choose to run the edge transport server in a multihomed setup where you have a network adapter connected to the internal network and one to the external network (perimeter network), you need to pay special attention in confi guring DNS. Since the external network adapter doesn’t have access to the DNS server in your Active Directory on the internal network, you should confi gure this network adapter to use a public DNS server (or a DNS server located in your perimeter network), so that the edge transport server can perform name resolutions, required to resolve SMTP domain names to MX or Mail Exchange records as well as route mail to the respective SMTP servers on the Internet. The internal network adapter should be confi gured to use a DNS server located in the perimeter network or, alternatively, to use a hosts fi le. As you saw in the section of this chapter titled “Enabling Name Resolution Lookups between the Edge Transport and Hub Transport Servers,” the edge transport and hub transport servers must be able to locate each other using name resolution. As was also the case with Exchange Server 2000 and 2003, you can confi gure the edge transport server to use a DNS server (typically an external DNS server) for routing mail other than the DNS server specifi ed on the external network adapter. In Exchange 2000 and 2003, this was done by taking the Properties of the default SMTP virtual server in the System Manager and then clicking the Delivery tab and fi nally the Advanced button. On an edge transport server, you confi gure the . used by the edge transport and hub transport servers. 2. Click Start | Administrative Tools and then click DNS. 3. In the DNS Management snap-in, expand the Server node and then Forward Lookup. File Figure 7.7 Purging and Preloading NBT Remote Cache Name Table 5. Save the changes and close Notepad. 6. Now open a Command Prompt Window by clicking Start | Run and then typing CMD.EXE. 7 snap-in and log off the internal DNS server. You may also choose to simply add the hostname and IP address of the edge transport server to the local hosts fi le on each hub transport server, and