JamesNT
Senior Member
Registered:1451917644 Posts: 142
Posted 1461529849
Reply with quote
#1
Should I configure both the internal and external to be mail.prodatamgmt.com or should I go with: External: mail.prodatamgmt.com Internal: exchange2013.ad.prodatamgmt.com JamesNT
__________________ I miss Windows NT 4.0 Service Pack 4.
cj_berlin
Senior Member
Registered:1451592353 Posts: 268
Posted 1461531492
Reply with quote
#2
James, personally, I would always try to go with as few namespaces as possible (in your case: one) which inevitably leads to split-horizon DNS. If you don't feel bad about doing split-horizon DNS, go with it. Makes obtaining SSL certificates easier, among other things. HTH
__________________ Evgenij Smirnov My personal blog (German): http://www.it-pro-berlin.de/ My stuff on PSGallery: https://www.powershellgallery.com/profiles/it-pro-berlin.de/
JamesNT
Senior Member
Registered:1451917644 Posts: 142
Posted 1461531700
Reply with quote
#3
I was hoping that would be the case, cj. Thank you. We use ZoneEdit for our external DNS hosting provider and, of course, all our internal Domain Controllers are also DNS servers. So we can use mail.prodatamgmt.com for both internal and external. ZoneEdit will point to our static IP assigned by our internet service provider, and the domain controllers will point to the internal IP address of the exchange server. Thank you! JamesNT
__________________ I miss Windows NT 4.0 Service Pack 4.