I don’t think he reads the Exchange list. ☺ From: [email protected] [mailto:[email protected]] On Behalf Of Richard Stovall Sent: Wednesday, May 7, 2014 4:33 PM To: [email protected] Subject: RE: [Exchange] new Exchange server
Cue Ben in: 3 2 1 On May 7, 2014 3:40 PM, "Michael B. Smith" <[email protected]<mailto:[email protected]>> wrote: Yes. You are correct. That is exactly what you want to do. It's called "Split DNS". Bing/google it. :) -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Craig Wardlaw Sent: Wednesday, May 7, 2014 3:12 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] new Exchange server I don't think I explained what I see as a problem. Right now all users have [email protected]<mailto:[email protected]> via hosted email . I have added the xxx.ca<http://xxx.ca> to the accepted domains on the exchange, added a rule to the firewall to direct any email sent to the xxx.ca<http://xxx.ca> domain to the exchange box but I read that the certificate issuers will no longer allow an xxx.local address on the cert. So I will have devices that will look for the internal autodiscover etc when inside the firewall but will need to look for the external when not on the network( blackberrys etc, not necessarily domain members) . So if I set up a dns zone for the xxx.ca<http://xxx.ca> on my internal dns to point to the exchange for autodiscover and OWA etc , then I will be able to use only the external url for both internal and external.So then can I just get a wildcard cert for the external domain name Sorry if this is a bit long winded or if I have the completely wrong end of the stick on how to accomplish this Cheers Craig -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Kennedy, Jim Sent: Wednesday, May 07, 2014 2:10 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] new Exchange server This is what I have been trying to figure out how to say since the OP. Just couldn't get the words right. -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Miller Bonnie L. Sent: Wednesday, May 7, 2014 1:58 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] new Exchange server Maybe I'm misunderstanding, but are you actually using xxx.local for internal e-mail addresses, or do all of your users have external addresses assigned that have the xxx.ca<http://xxx.ca> domain name attached somewhere? If the latter, just use the external name only and publish that name to all internal users and locations--no domain rename required. -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Craig Wardlaw Sent: Wednesday, May 07, 2014 10:11 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] new Exchange server I am currently setting up a single exchange server to replace hosted email and after doing some reading it looks like getting the appropriate cert for it may cause more issues. I have the internal domain xxx.local and the external domain xxx.ca<http://xxx.ca>. From Google I see that I will no longer be able to get the internal and external domains on the cert and there are a couple of ways to mitigate the problem, I'm not a fan of migrating the domain considering I'm pretty much the only IT person. Just wondering how some of the list people are or have dealt with this Thanks Craig
