Concerning the mx record, that is already being managed by a 3rd party name service provider. It will not have to change since we are not getting a new external IP address. A representative from that company, though, said that some DNS settings will have to change on my end to make sure that mail is routed properly to the new server instead of the old (primary) server where we are currently set up using different mail server software. (We are transitioning from MailEnable to MS Exchange Server 2007).
Can anyone offer any advice concerning these DNS settings? Or do you have any other useful tips to help me have a smoother transition? (I didn%26#039;t install our first mail server, and this is my first time installing Exchange Server).
Thanks,
Riven|||Riven,
Non-microsoft DNS servers that are authoratative on your network must support 2 DNS standards; service resource records and the DNS dynamic update protocol.
Outlined in RFC 2052, a service resource record (SRV RR) is a type of DNS record that enables DNS to recognize multiple servers in a single domain and to locate commonly used TCP/IP services that are associated with specific servers. SRV RRs allow a DNS server to generate a list of network servers that provide TCP/IP services and the protocols supported by those servers, and to determine a preferred server for a specific service, such as Microsoft Exchange.
The SRV record is formatted to include information about the service that is provided by a server, the domain that is serviced by a server, and the protocol used by the server.
The DNS Dynamic Update Protocol is outlined in RFC 2136 and enables information in a DNS server to be automatically updated, i.e., enabling a W2K Pro workstation to update its DHCP-leased IP address
The last piece of advice I can give you is to trust your software. MS Exchange is pleasantly intuitive and forgiving as long as your ducks are in a row. By that I mean your primary DNS server is (or should be) the authoratative server for that zone. This means that all changes to the zone, the creation of address (A) resource records, new SRV resource records, and so forth must be made on that DNS server.
You have the option to create one or more backup DNS servers, called secondary DNS servers, for a primary DNS server. A secondary contains a copy of the primary%26#039;s zone database, but is not used for administration.
Make sure that you complete two steps in the windows 2k server environment. First, configure W2K DNS zones in a domain particularly the forward and reverse lookup zones, to accept dynamic updates by opening the DNS tool in administrative tools, displaying the zone and its child objects in the tree, displaying the child objects under the domain, right clicking the domain under the zone, and clicking properties. Second, if you%26#039;re using DHCP Riven, configure it to dynamically updateDNS or to have clients perform the dynamic update. To configure DHCP, open the DHCP tool in the Administrative Tools, right-click the DHCP server in the tree, click properties, and click the DNS tab. Please don%26#039;t be offended if I%26#039;ve repeated a lot of what you already know, I just meant to cover all the bases. Good luck.|||Hope this helps?
http://technet.microsoft.com/en-us/libra鈥?/a>
