Hi all !When I execute an NSLOOKUP in my domain to checkout my email configuration, oddly enough I keep getting my former Exchange 2003 server I.P address !Today I came acrossthis record couldn't locate, adding an "autodiscover" record !.In my DNS console, more especially in the "_mydomain" directory (see below):DNS MYSERVER Forward Lookup Zones + Mydomain.fr + _msdcs .... + _forestdnszones + _fr + _mydomain...I have the "former" record of my decommissioned server !!!Furthermore, when I created an "autodiscover" record, it was automatically stored there.My question is very simple : is this the right directory where the "autodiscover" record should be stored, and is this normal that my former MX record is still there ?Originally it was locatedin the root directory of my DNS records, that's the same place as my current MX record for my new Exchange 2007 record !I guess that the decommissioning process moved the record in this directory !Should I simply delete it and recreate my current MX record there ?Thx for your help !PhiL.

Not sure if I understand you correctly.However, if at all -- and most likely not -- your MX record and your A or CNAME record for Autodiscover should be created in Mydomain.fr, not below. It is not normal to store a MX record in + _mydomain.In many cases you do not need an MX record in your internal DNS. That is, this depends on your internal mail flow. For instance if you want to mail-enable SharePoint folders, you would need to create an MX record for your SharePoint server. If you have a foreign SMTP server on your internal network, you might need an MX record to point to your Exchange Hub Transport server.All your domain-joined clients won't need an Autodiscover record. They will look up the needed information in the Active Directory through a Service Connection Point (SCP). For clients that are not members of your domain, you might need an Autodiscover record. These are clients, such as an iPhone, Mac OS X Snow Leopard and MS Office Entourage 2008. You could create a record for these clients on your internal DNS or let them use the record you have created on your public DNS. The best approach here is to use a split-brain DNS: Your public DNS name resolves to a public IP address and an internal private IP address. I have never seen a decommissioning process moving any MX record, nor an Exchange installation that creates an MX record. An MX record is a type of a DNS record that must be explicitly entered. It either exists or it doesn't. Creating MX recordshttp://technet.microsoft.com/en-us/library/cc505889.aspx Autodiscover and Exchange 2007http://technet.microsoft.com/en-us/library/bb232838.aspx Macs discover AutoDiscover: Exchange Server Support in Snow Leopardhttp://exchangepedia.com/blog/2009/06/macs-discover-autodiscover.html Jon-Alfred Smith MCTS: Messaging MCSE: S+M

Hi Jon-Alfred, First of all, thx very much for this detailed answer !>Not sure if I understand you correctly.However, if at all -- and most likely not -- your MX record and your A or CNAME record for Autodiscover >should be created in Mydomain.fr, not below. It is not normal to store a MX record in + _mydomain.I didn't store them myself !As I explained in my email, I came across this MX record that I thought the decommissioning process had removed by itself !>In many cases you do not need an MX record in your internal DNS. I agree Jon-Alfred !>That is, this depends on your internal mail flow. For instance if you want to mail-enable SharePoint folders, you would need to create an MX record >for your SharePoint server. If you have a foreign SMTP server on your internal network, you might need an MX record to point to your Exchange >Hub Transport server.Yes, this is one of the main reasons I need it.>All your domain-joined clients won't need an Autodiscover record. They will look up the needed information in the Active Directory through a >Service Connection Point (SCP). For clients that are not members of your domain, you might need an Autodiscover record. These are clients, such >as an iPhone, Mac OS X Snow Leopard and MS Office Entourage 2008. Didn't know, and I'm very interested in this !>You could create a record for these clients on your internal DNS or let them use the record you have created on your public DNS. The best >approach here is to use a split-brain DNS: Your public DNS name resolves to a public IP address and an internal private IP address. At the beginning, what led me to create this record was that I had noticed an "error code 0x8004010F when trying to download an OAB" ona laptop with Outlook 2007 installed.Another Microsoft KB article was also talking about an SRV record that could do the same thing !So, should I understand that this error is not necessarily linked to an unsuccessful query to locate the autodiscover process ?>I have never seen a decommissioning process moving any MX record, nor an Exchange installation that creates an MX record. So, you're as puzzled as I'am ! ;-)If the decommissioning process didn't move the record, I don't know what did it !But what I can tell for sure isthat this MX record had initially been created by me, MANUALLY, when I first installed the Exchange 2003 Server 5 years ago and it was still at the same place before the migration !>An MX record is a type of a DNS record that must be explicitly entered. It either exists or it doesn't. Yes, we both agree on this point ! ;-)I eventually deleted this "old" MX record, and now I get my new Exchange Server when doing an NSLOOKUP for MX type ! ;-)Thx for your advice,PhiL Jon-Alfred Smith MCTS: Messaging MCSE: S+M

Good to hear. While off topic, just a few comments: OAB on Windows 2008 once next-to drove me insane. Turned out to be related to kernel mode authentication (fixed with rollup 8 and higher). Before we manually changed to user mode authentication (Rollup 6), I had the opportunity to study the ins and outs of OAB. Here is a real good starting point:Offline Address Book web distribution in Exchange Server 2007 http://msexchangeteam.com/archive/2006/10/16/429204.aspxAs to Autodiscover, you can use a SRV record. I do, the main reason was because my SAN / UC certificate generated by SBS 2008 did no contain autodiscover.domain.com:Updated White Paper: Exchange 2007 Autodiscover Servicehttp://msexchangeteam.com/archive/2007/10/03/447176.aspxJon-Alfred Smith MCTS: Messaging MCSE: S+M