Exchange 2013 DNS
-
Having issues with DNS records for an Exchange 2013 server build in Windows 2012 environment. My boss gave me a 5 minute crash course on DNS and then I was left to my own devices. I watched some videos, read some articles, but ultimately my inexperience led me to make these records, and I'm not sure they are correct as the Exchange services are not functioning. I'm not so concerned with getting help to make the Exchange server work, I'd just like a little insight from the bright minds of MangoLassi on if and how I messed up here. The goal here is to get a better understanding of DNS.
*EDIT: AD and DNS reside on same server. Exchange is separate.
~ON DNS SERVER
Record Type - Record Name - Record Value (Data)CNAME - autodiscover - mail.contoso.com
A - mail - ExchangeServerIP
MX - ExchangeServerName - mail.contoso.com
CNAME - owa - mail.contoso.com~ON HOST (PUBLIC FACING)
Record Type - Record Name - Record Value (Points to)CNAME - autodiscover - mail.contoso.com
A - mail - OutwardFacingIPofExchangeServer
MX - ExchangeServerIP - mail.contoso.com
CNAME - owa - mail.contoso.com -
Where is your DNS? AD? Then you also have to do everything on your public DNS with your public IP.
-
Use this to dump everything out.
https://gallery.technet.microsoft.com/E2010-2013-Export-Exchange-df0112a2Then set everything that is wrong on both your AD DNS and public DNS.
-
It outputs this data. I just ran this on a Server 2012 R2 + Exchange 2013 server.
Service URI OAB-ExernalURL https://remote.domain.com/OAB OWA-vDirNAme owa (Default Web Site) OWA-InternalURL https://remote.domain.com/owa OWA-ExernalURL https://remote.domain.com/owa ECP-vDirNAme ecp (Default Web Site) ECP-InternalURL https://remote.domain.com/ecp ECP-ExernalURL https://remote.domain.com/ecp AutoDisc-vDirNAme EXCH01 AutoDisc-URI https://remote.domain.com/autodiscover/autodiscover.xml EWS-vDirNAme EWS (Default Web Site) EWS-InternalURL https://remote.domain.com/ews/exchange.asmx EWS-ExernalURL https://remote.domain.com/ews/exchange.asmx OutlookAnywhere-InternalHostName(NoneForE2010) remote.domain.com OutlookAnywhere-ExternalHostNAme(E2010+) remote.domain.com -
Then just google each service name for the powershell to change it.
-
@jaredbusch Hey I appreciate you providing me with this. I'm kind of new to Windows Powershell as well.
I right clicked this file on the Exchange Server and selected "Run with Powershell". It prompts me that "Export-ExchangeURL_time_date_etc file doesn't exist, do you want to create it?"
I say yes.
Then it opens up a text document that's blank. that's all that happens. There is no file created.
Then tried it on DC instead of Exchange Server. Same thing, only this time it made the file, but it's still blank.
-
Open power shell with administrator rights, change directory to wherever you have the script saved.
./scriptname.ps1Do this on your exchange server.
-
Also you can run the following commands to get all the virtual directories
get-AutodiscoverVirtualDirectory get-ClientAccessServer get-webservicesvirtualdirectory get-oabvirtualdirectory get-owavirtualdirectory get-ecpvirtualdirectory get-ActiveSyncVirtualDirectory -
@jaredbusch quick question. How did you take what it output and make it so fancy looking on this comment thread?
-
@g-i-jones said in Exchange 2013 DNS:
@jaredbusch quick question. How did you take what it output and make it so fancy looking on this comment thread?
Quote his post and look at his formatting.
-
@dashrender thanks, bro.
-
@g-i-jones said in Exchange 2013 DNS:
@jaredbusch quick question. How did you take what it output and make it so fancy looking on this comment thread?
Well first i opened the CSV in Office and transposed the output because it made it all across the top.
Then I used this to create the markdown table.
https://donatstudios.com/CsvToMarkdownTable
Note: Even though it says CSV to Markdown, you can copy/paste right out of Excel/CalcManually making a table in markdown is stupid.
