CapnPugwash Posted February 10, 2015 Posted February 10, 2015 Hi, We run Exchange 2010 on site. We have recently changed our external domain name from oldschool.county.com to newschool.county.com. Our internal domain name is the same (oldschool.internal) for the next few months BOTH external domain names will exist In a months time the old domain will not exist, we have no control over this. All our staff use OWA to access their email from home, currently they log in via https://mail.oldschool.county.com but I need to change it so that they can access mail via the new address I have a new SSL cert for the Exchange server. I have installed is but not assigned it to any services (in Server Configuration -> Exchange Certificates) I *think* before I do that I'm going to have to do something with MX records. In DNS I have a record for mail.oldschool.county.com that points to exchange. From what I've read (not understood!) I should be able to create a 2nd MX record called mail.newschool.county.com & point it to Exchange without causing myself any problems Then if I go to Exchange (Server Configuration -> Exchange Certificates) and assign the services to my new SSL ... everything should work ok.... Any advice welcomed! This is the kind of thing that gives me kittens... NOTE : I've set up the new mail addresses and they work fine. Staff receive email sent to either [email protected] or [email protected], the new address is set as the primary address
CapnPugwash Posted February 10, 2015 Author Posted February 10, 2015 Hmmmm Not quite as I thought. I've just tried to create a new MX record,the FQDN info is already there and can't be changed. It's set to mail.oldschool.county.com
CapnPugwash Posted February 10, 2015 Author Posted February 10, 2015 OK... Maybe somebody is reading this?! Hope so. I can't actually find the original MX record in DNS. I have a forward lookup zone called mail.oldschool.county.com - when I try and create a new MX record here, it has the FQDN hardwired in - mail.oldschool.county.com If I try and create a new MX record anywhere else, this is not the case. I've got to figure this out, I do have a good week to do it, so it should be do-able(!) Like I said before Any advice welcomed!
Roberto Posted February 10, 2015 Posted February 10, 2015 It sounds a lot like you're trying to create mail.newdomain.com as a record in the oldschool.county.com zone. That simply will not work. You need to create a new DNS zone for the new domain name if you haven't already. Have you, or someone else, done that? Once you've done that you can create a new A record for the IP address of the mail server, and then a MX record pointing to that address. 1
CapnPugwash Posted February 10, 2015 Author Posted February 10, 2015 Hi Roberto, Thanks for the reply. To be honest I think I'm in a bit of a tangle and the information I'm giving you all is most certainly NOT the best, mainly because I have a limited understanding of what it is I'm doing. DNS & Email has been set up / tinkered with by various people over the last 10 years. Now there is just me. Getting a third party in to sort this is a definite no no. Back tracking a little bit. Our new external domain name is to reflect the recent name change of the school. Our internal domain name is unchanged. I have installed the SSL certs for the website & VLE & these work fine. I only have to sort out the SSL for Exchange. I've installed the cert on Exchange but the services (IMAP, POP, IIS, SMTP) are still assigned to the old SSL for the old domain name. I did try assigning the services to the new SSL cert but OWA didn't work as expected - I either couldn't connect locally or I couldn't connect externally - I can't remember which & I haven't had time to re-check The domain host (County) has MX records pointing to our Exchange server from both the old domain name and the old domain name I assume that I need a local MX record for internal emails? I can't find an MX record in local DNS but there is a forward lookup zone called mail.olddomain.county.com If I run nslookup set type = mx & point it at mydomain.internal, it doesn't return any MX info. If I point it at olddomain.com or newdomain.com it gives me info on the MX record that our domain host has... It could be that I'm barking up the wrong tree(s) with all of this....
pleach85 Posted February 10, 2015 Posted February 10, 2015 Sounds to me like your MX records are sorted now so you can move on to your dns records Create a new forward lookup zone mail.newschool.county.com and create a host A record with a blank name and the internal IP of your mail server. Update your external DNS so that mail.newschool.county.com points to the same IP address as mail.oldschool.county.com did/does (this might have been done by county already) You should then be able to browse to OWA using your new external domain name, once you've checked you can assign the new SSL certificate.
CapnPugwash Posted February 10, 2015 Author Posted February 10, 2015 OK, in DNS I've created a new forward lookup zone 'mail.newdomain.com' Within this zone I've created a new 'A' record pointing at the Exchange server & an MX record pointing at the 'A' record. Am I done? Is it as simple as assigning services in Exchange to my new SSL?
CapnPugwash Posted February 10, 2015 Author Posted February 10, 2015 Sounds to me like your MX records are sorted now so you can move on to your dns records This is (one of the many) bits I'm confused by... are my MX records sorted? They are sorted by externally by our ISP/County but do I need MX records in the internal DNS? & if so why can't I find an MX record for in internal DNS for 'mail.oldomain.com' ? Thanks for your reply - much appreciated
pleach85 Posted February 10, 2015 Posted February 10, 2015 Locally you shouldn't need any MX records. Try browsing to https://mail.newdomain.com/owa and see if it's working... you'll get an invalid SSL warning, but that will obviously go away when you assign your new SSL. 1
CapnPugwash Posted February 11, 2015 Author Posted February 11, 2015 Locally you shouldn't need any MX records. Try browsing to https://mail.newdomain.com/owa and see if it's working... you'll get an invalid SSL warning, but that will obviously go away when you assign your new SSL. Great ! Thanks everyone for all your help
CapnPugwash Posted February 13, 2015 Author Posted February 13, 2015 Well, in DNS I have set up a forward lookup zone for mail.newdomain.county.com, in this zone I've created an 'A' record that points at Exchange In Exchange I've assigned IMAP, POP, IIS, SMTP services to the new SSL cert. If I login to OWA on my phone it works fine If I login to OWA while on the local network I get a cert error Do I need an internal self signed cert... or....? Nearly there!
CapnPugwash Posted February 13, 2015 Author Posted February 13, 2015 (edited) The Cert error is 'The security certificate presented by this website was issued for a different website's address' Also, if I type https://mail.newdomain.county.com , I get the cert error above. If I click on 'Continue to this website (not recommended)' it takes me to the logon page but changes the root of the URL to https://mail.olddomain.county.com ... Edited February 13, 2015 by CapnPugwash
CapnPugwash Posted February 13, 2015 Author Posted February 13, 2015 I've had a look in DNS, the zone for the old mail address is still there (mail.olddomain.county.com) - opening it up I can see an SRV record (ldap , _tcp) that ties the port 443 to mail.olddomain.county.com I've created the same record in my mail.newdomain.county.com zone to point port 443 to the new address but I still have the same issue.. on the internal network if I go to the new https://mail address it throws the above cert error. If I click 'continue' it takes me to the mail logon page but changes the root of the URL back to the old domain name...
pleach85 Posted February 13, 2015 Posted February 13, 2015 Sorry, I've overlooked something. You will also need to update Exchange with new URL, the below technet article tells you how to do it. I would run the get commands first ( i.e. get-AutodiscoverVirtualDirectory | FL ) and document the output just in case you need to revert. Managing Exchange 2010 External/Internal URL's via PowerShell - TechNet Articles - United States (English) - TechNet Wiki 1
CapnPugwash Posted February 13, 2015 Author Posted February 13, 2015 Sorry, I've overlooked something. You will also need to update Exchange with new URL, the below technet article tells you how to do it. I would run the get commands first ( i.e. get-AutodiscoverVirtualDirectory | FL ) and document the output just in case you need to revert. Managing Exchange 2010 External/Internal URL's via PowerShell - TechNet Articles - United States (English) - TechNet Wiki I've just realised that myself! Thanks for the link
pleach85 Posted February 13, 2015 Posted February 13, 2015 No problem, you might want to update your HELO/EHLO on any receive connectors you've got too (server conf -> Hub Transport -> Receive Connectors).
CapnPugwash Posted March 18, 2015 Author Posted March 18, 2015 Well... I'm hating to come back to this... but here I am.... I assign services to the SSL cert I make changes in : (Server -> Client access) Outlook Anywhere , OWA SETTINGS , Outlook Web App, Exchange Control Panel, Exchange Activ Sync, Offline Address Book - pointing them all to the new mail.myNewDomain address In DNS , Forward Zones, mydomain.internal/_tcp there is an _autodiscover record, pointing to mail.myOldDomain , I change this to point to the new one. There is zone in forward zones called mail.myOlDomain, I create a new one to point at the mail.myNewDomain I can't see any A or C records point at mail.myOldDomain... only A records pointing at Exchange itself I can see the DNS changes have propagated over to my second DNS server When I enter https://mail.myNewDomain, the URL changes to https://mail.myOldDomain & throws an SSL cert warning... Either there is still a setting in Exchange I need to change? Or there is something in DNS that I need to change?
pleach85 Posted March 18, 2015 Posted March 18, 2015 It sounds like you've covered everything in DNS and Exchange, so I can only assume there is a rule in IIS that is redirecting you to the oldDomain. A rule is often created to redirect the root (https://mail.domain) to https://mail.domain/owa, there are a few ways this can be done (error page redirect, URL Rewrite ....) so it looks like you're going to have to spend a little time trying to find out if there is anything like this in IIS. 1
CapnPugwash Posted March 19, 2015 Author Posted March 19, 2015 It never occurred to me to look at IIS, straight away I can see a HTTP redirect that points at the old domain name - Thanks!
CapnPugwash Posted March 24, 2015 Author Posted March 24, 2015 All sorted! I never needed to look at DNS, the settings were all in Exchange /IIS. Thanks everyone who chipped in with useful ideas
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now