2012 r2 -Microsoft Exchange 2013 DNS timed out

I just installed Microsoft Exchange 2013 on my 2012 r2 server. I just installed all of the Roles &features, then I went to my fire walls and then I disabled them (temporarily). I configuring my IP addressing, DNS Ip address and a dns suffix. Now I
can't access my Exchange via browser so I did some trouble shooting and sure enough I can't ping my DNS address. I can ping my IP address though. If anyone has any suggestions that would help then let me know. Thank you for any responses!

Hi Dallen,
>>Now I can't access my Exchange via browser so I did some trouble shooting and sure enough I can't ping my DNS address.
It is not a hyper-v issue , it's more like a network problem .
First , I would suggest you to disable firewall in DNS server for troubleshotting .
If firewall is truned off then you still can not ping the DNS server , you may check if the exchange server can ping other IP address in your LAN to check network conectivity .
If they are in different subnet ,you may try to check the configuration of the router .
Any further information please feel free to let us know .
BestRegards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Can't get OWA to work on Essentials 2012 R2 with Exchange 2013 on second server 2012 R2 std.

I have previously with success setup a working solution with server 2012 essentials, and a second server 2012 std. with exchange 2013, I did it following this guide: http://technet.microsoft.com/en-us/library/jj200172.aspx
Unfortunately I lost the server due to a cooling error which led to an un-repairable essentials 2012, since this was a new setup and also a test setup I didn't have any working backup solution setup at the time...tsk.tsk.
Since I had to make a complete do over I chose to try out the new R2 server editions, and set it up following the same guide, when it came to this part:
Download KB2732764 for ARR 2.5, and then install the update on the server that is running Windows Server 2012 Essentials.
Copy the SSL certificate file for Exchange Server to the server that is running Windows Server 2012 Essentials. The certificate file must contain the private key, and it must be in the PFX file format.
Note
If you are using a self-issued certificate, follow the instruction in the Exchange Server article Export an Exchange Certificate to export the certificate.
Open a command window as an administrator, and then open the %ProgramFiles%\Windows Server\Bin directory.
Based on you installation scenario, follow one of these steps to configure ARR:
If you are performing a clean setup, run the following command:
ARRConfig config –cert “path to the certificate file” –hostnames “host names for Exchange Server”
I noticed that the version of "Application request routing" had changed to version 3, so obviously I didn't need to dl the 2.5 update.. When I came to the part where I wa instructed to run arrconfig config etc. I noticed
that the ARRconfig file no longer where placed where the setup guide indicated, I then went ahead and tried som manual configuration regarding certificates and such. In the end I have a working solution where Exchange and OWA is working locally but OWA isn't
working outside my local domain, the link get's placed in the RWA and is indicating the correct link for the exchange server www.remote.clinten.dk I have a certificate which include to separate domain names aforementioned and remote.clinten.dk and
I get no errors indicating certificate errors, when I try to connect to www.remote.clinten.dk/owa from outside I get a 404 error, and when I connect to www.remote.clinten.dk I get the RWA login screen for the essentials RWA. Obviously I need to set up something
in ISS probably in the url rewrite section, but I can't seem to find the right setting.. Can someone help with this?
Btw. I have found the missing arrconfig file in c:\windows\system32\essentials" and tried to run the command as described in the guide "ARRConfig config –cert “path to the certificate file” –hostnames “host
names for Exchange Server”" but it doesn't seem to work, it just prompts with a guide for using the arrconfig command and examples of correct use, I also tried removing the "" from the guide, like this "ARRConfig
config –cert path to the certificate file –hostnames host names for Exchange Server",
when I ran it without the "" It didn't prompt me with anything nor did It indicate any errors, it did not however make my OWA work either..
I am aware that exchange 2013 atm. isn't officially supported on the R2 server, but the exchange works fine inside my domain, and the pop3/smtp also works from outside, since this Is a test environment, using only my own private domain and not a company
domain I figured it would be ok to run the risk.. ;)

Hi
found this on
https://social.technet.microsoft.com/Forums/en-US/1f099068-b3ed-44f3-a8c4-c22d760a8621/arr-broken-or-bad-syntax-exchange-2013-essentials-2012-r2?forum=winserveressentials
"Ok just an update for anyone else how has this issue.
The problem has been solved by Microsoft and I have included their findings below, but basically it comes down to a typo!
I often use notepad to have all the commands I need on hand, and I must have copied the command direct from the TechNet article or other website and customised the required fields. The issue with this is one of the characters did not “convert” - for want
of a better word. I should have retyped the whole command from scratch and it would have been right!
Thanks for everyone’s input and for Microsoft for getting to the bottom of it.
From Microsoft:
We have tested on your environment and here is the investigation result from our senior engineer:
================================================================
Basically the command fails due to invalid parameter, the invalid one is the ‘-‘. I think the one customer used is copied from the online document sample which translate to the unicode is 0x8211 means “en dash”, it
can’t be input by normal keyboard, so I pretty sure it is from web (mostly HTML document).
The one we check (compare) is ‘-‘ which has the code 0x45.
So it always failed to compare the parameter and ARRconfig.exe thought it is invalid parameter.
The solution is quite simple, just using keyboard to retype the command, using normal ‘-‘ and I have tried the password prompt shows
Best Regards,
Johnny Chen
Microsoft Partner Support Community Technical Support Engineer
Microsoft Global Partner Services"

Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
move them to the new server and mount them and relocate the mailboxes?
Frank.

Hi,
According to your description, I recommend you consider using DAG to achieve your requirement.
The following steps for your reference:
1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
3.After replication, you can mount all the databases on the new server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
Please Unmark it!
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Slow PowerShell execution of Microsoft Exchange 2013 commands from c#

I have the following code that executes an exchange cmdlet. It works fast with command that return some output but work slow if command has no output.
for example
Invoke("Get-Mailbox")
prints following output:
Begin execution at 11:44:43
Finish execution at 11:44:51
Output :
Administrator
Discovery Search Mailbox
Artem Romanchik
Execution time was about 8 second(6 second for loading exchange snappin + 2 seconds for command execution)
Slow example is
Invoke("Set-Mailbox -identity tema -MaxSendSize 10MB")
Begin execution at 11:53:34
Finish execution at 11:54:36
Output :
Now it was 62 seconds(2 seconds for command and 60 seconds of waiting for something)
How can I reduce execution time of second example?
Invoke method code:
public void Invoke(string command)
var config = RunspaceConfiguration.Create();
PSSnapInException warning;
config.AddPSSnapIn("Microsoft.Exchange.Management.PowerShell.Snapin", out warning);
using(var runspace = RunspaceFactory.CreateRunspace(config))
runspace.Open();
using(var _psInstance = new RunspaceInvoke(runspace))
var psCommand = new PSCommand();
Console.WriteLine(String.Format("Begin execution at {0}", DateTime.Now.ToLongTimeString()));
var result = _psInstance.Invoke(command);
Console.WriteLine(String.Format("Finish execution at {0}", DateTime.Now.ToLongTimeString()));
var output = "";
foreach (var line in result)
if (line == null)
continue;
output += "\n" + line.BaseObject.ToString();
Console.WriteLine(String.Format("Output: {0}", output));
runspace.Close();

On 2010 and 2013 Powershell is throttled
http://technet.microsoft.com/en-us/library/dd298094(v=exchg.150).aspxyou might want to do some testing with a user that has throttling policy disabled. Also you might want to check the logs on the CAS server the request are going through eg \Microsoft\Exchange
Server\V15\Logging\CmdletInfra you should be able to determine from these if your being throttled.
Cheers
Glen

Exchange 2013 DNS for internal and external domain

Hi All,
I have been assigned a task to implement Microsoft Exchange Server 2013. I need some help in setting up DNS namespaces and design a strategy to have same internal and external names. Let me share some details here.
We have an Active Directory domain myinternaldomain.net, and we have a public domain
mypublicdomain.com and we have setup email policy to have
mypublicdomain.com as the SMTP domain for all the users. We have created another DNS zone in Active directory integrated DNS and created a records for
mail.mypublicdomain.com and autodiscover.mypublicdomain.com which will point to CAS NLB IP. We have 2 CAS servers and 2 MBX servers, we have configured DAG for MBX High availability and planning to implement WNLB for CAS as
hardware LB is out of scope due to budget constrains.
We want to have same URLs for OWA, Autodiscover, ECP and other services from internal network as well as from public network. Users should not be bothered to remember two URLs, using one from internal and other from public networks. I also want to confirm
that with this setup in place do i need to have myinternaldomain.net and server names in SAN certificate?
Thanks

Hi Sccmnb,
You can easily achieve this using split DNS.
Internal DNS hostname "mail.mypublicdomain.com" will be pointing to your internal CAS NLB IP and the external public DNS hostname"mail.mypublicdomain.com" will be pointing to the Network device or
Reverse proxy server IP.
Depending upon users access location(internal\external) the IPs would vary and they should be able to access the website with same name.
The names that you would require on the certificate(Use EAC or powershell to raise the request) for client connectivity would be
SN= mail.mypublicdomain.com
SAN= autodiscover.mypublicdomain.com
You don't need to have the active directory domain name present in the certificate.
Additional to this you need to update the AutodiscoverURI for all servers and OWA,ECP,Autodiscover Virtual Directories InternalURL and ExternalURL fields with appropiate public names.
Some additional Info:
*Internal vs. External Namespaces
Since the release of Exchange 2007, the recommendation is to deploy a split-brain DNS infrastructure for the Internet-based client namespaces. A split-brain DNS infrastructure enables different IP addresses to be returned for a given namespace
based on where the client resides – if the client is within the internal network, the IP address of the internal load balancer is returned; if the client is external, the IP address of the external gateway/firewall is returned.
This approach simplifies the end-user experience – users only have to know a single namespace (e.g., mail.contoso.com) to access their data, regardless of where they are connecting. A split-brain DNS infrastructure, also simplifies the configuration of Client
Access server virtual directories, as the InternalURL and ExternalURL values within the environment can be the same value.
*Managing Certificates in Exchange Server 2013 (Part 2)
*Nice step by step article
Designing a simple namespace for Exchange 2013
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

SCCM 2012 SP1 and Exchange 2013 Connector Get-Recipient cmdlet failed

I have been trying to get my Exchange Connector working with SCCM 2012 SP1 for a week or so now. Every post tells me that the Get-Recipient cmdlet failed is a security permissions error. I have given the service account running the connector full Exchange
Server Management rights including Recipient Management and Organization View-Only. I have even tested remote power shell to the CAS server and run the cmdlet with no issues.
For some reason it just does not want to work for me. Has anyone been running into this issue?

Now before you read the following error and say oh this is a permission issue I am telling you it is not. I have given the account full Exchange admin rights and I have even tested the Get-Recipient cmdlet remotely to the Exchange server and it works with
no issues. I have also noticed multiple forum posts with the exact same issues.
I have noticed one thing that stands outs "Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean"
I believe this issue may be related to changes in the powershell commands with Exchange 2013, but I do not know where or how to edit the ps1 script.
I am getting the error below:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to
type System.Boolean."~~ at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings
settings)~~ at System.Management.Automation.PowerShell.Invoke()~~ at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
STATMSG: ID=8817 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_EXCHANGE_CONNECTOR" SYS=MySite SITE=MySiteID PID=xxx TID=xxx GMTDATE=Thu Sep 19 07:00:01.653 2013 ISTR0="Get-Recipient" ISTR1="ParameterBindingFailed,Microsoft.Exchange.Management.RecipientTasks.GetRecipient"
ISTR2="Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)

How to configure AD on windows 2012 server for Exchange 2013 internal and external email flow

Dear Experts,
I have to configure exchange 2013 on Windows server 2012 STD. Company has registered Static IP addresses and can get the MX record pointing to any of this Static IP.
The registered domain name is e.g. contoso.com.
a. What should I use as domain name on AD? contoso.com or contoso.local
b. Is it recommended to have two different servers for AD and Exchange?
c. What should be my connector settings for mail flow?
d. how can I set 2 email servers in company for load balancing?

Hi,
a, I suggest use contoso.com as domain name. It is convenient to add urls into our certificate for internal and external mail flow.
b, Recommended that installing AD
and Exchange Server on two separate
Servers. If Exchange Server downed unfortunately, it can prevent AD server from crushing at the same time.
c, Found some articles for your reference:
Configure Mail Flow and Client Access
http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
Configuring Outbound Mail Flow in Exchange Server 2013
http://exchangeserverpro.com/configuring-outbound-mail-flow-in-exchange-server-2013/
d, Load Balancing
http://technet.microsoft.com/en-us/library/jj898588(v=exchg.150).aspx
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

SBS2011 - Cross domain Migration to Server 2012 R2 w/ Exchange 2013

I am attempting to find the best way to do this, and any input/guidance would be greatly appreciated.
Source Server: SBS 2011 Standard - Internal domain costco.local
Target Server: Server 2012 R2, 2 virtuals, one for the domain controller, one for Exchange 2013 - Internal domain ad.costco.com
I know that in order to establish a trust relation, I must add a secondary domain controller to the SBS2011 domain and transfer FSMO roles. My question is, can I use a trial Server 2008 R2 as an interim DC, create the trust, use ADMT to migrate user
accounts to the new domain and move mailboxes from the SBS server with the trust established on the Server 2008 DC? Or do I have to install an interim exchange server and move the mailboxes and remove the SBS server from the domain?
If that is the case, can I use a 180 Trial of Server 2008 R2 and Exchange 2010 on two separate virtuals on the old domain, move all user accounts and mailboxes to a standard domain temporarily. Then from the standard domain move user accounts and mailboxes
to the Server 2012 R2 DC and Exchange 2013 virtual?
It would be great if I could just establish a trust with with a second DC with SBS and move user accounts and mailboxes to the new internal domain, but I'm not sure if that is possible. Any insight would be greatly appreciated!

SBS can't do trusts but the migration prep tool temporarily allows them I believe. Have a look at this link dealing with migration to 2012 essentials from SBS, it doesn't deal with exchange though:
https://technet.microsoft.com/en-us/library/jj721754.aspx
There is also a recent thread "Migrating from SBS 2011 to Server 2012R2 Standard & Exchange 2013" that may have some info.
-- Al

Why Do i need SCOM 2012 R2 with Exchange 2013 ?

This is a question is commonly asked now a days with the "Managed Service" Feature of Exchange 2013 , why do I still need SCOM for just my Exchange monitoring ?
I have my understanding that still with managed service in exchange there are several component's that needs to be monitored outside the managed service , but I am looking for some nice bullet points.
Please help.

If you are a small shop, then you may not need to spend the money on SCOM to monitor Exchange 2013. However, if you have a large deployement, then you might want to have System Center OM.
While Exchange 2013 does store performance data (configurable I believe) for maybe seven days, you will not have long term trend and performance data. I understand the Exchange 2013 MP is not collecting performance, but this doesn't mean you cannot
replicate what it is doing in a custom management pack for Exchange 2013. Now you will have a single repository for all of your Exchange 2013 servers, where you can see performance history, look at trends, etc.
Furthermore, events that might help you with KHI are going to roll out of the event logs on your exchange servers, unless you are archinving that data, even then, with no centralized location, it will be very hard to keep track of the issues you have experienced.
With SCOM agents sitting on those servers, that data will be stored, again, in a single database, where you can report on KHI's and what not (SLO/SLA included).
Furthermore, we know Exchange 2013 runs checks on potential failover candidates. These checks should come back healthy in order for the server to be considered a good failover candidate. What if these checks detect an issue with a potential failover
candidate? Wouldn't you like to know, so that you can address that before it impacts the Exchange service? Again, this is where SCOM would come in, not just for monitoring for these things, but other issues like network, hardware, software, OS,
etc.
So, like I said, if you are a small shop, you can probably forgo the expenses. If you have a large 2013 environment, then SCOM will be beneficial, but understand that you will probably have to add too the Exchange 2013 managememt pack in order to get
the most out of it (since they stripped this latest version down compared to E2K10 MP).
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

Server 2003 SBS (with Exchange 2003) migrate to new machine Server 2012 Standard (with Exchange 2013)

This is what I have:
A very outdated machine running a small domain, SBS 2003 and Exchange - this is the ONLY server currently.
This is what my boss ordered:
A Dell R210 II machine with Server 2012 Standard (and I downloaded the trial for Exchange 2013).
He wants the old server completely replaced and gone - with everything moved over (including Exchange) to the new machine. The main reason for the upgrade is that not all users can access email on their machines (Macs, new versions of Outlook, etc.)
I have set up a new standalone server before but never migrated one - and I've found that going from SBS2003/Exchange2003 to Server2012/Exchange2013 is not simple in the least.
I thought I could just set up the new server as a DC on the domain and have everything replicated to it from the source server. Then I could decommission the old server. I have been told that 1) I can't upgrade Exchange 2003 to 2013 and 2) that I shouldn't
put Exchange on a DC. What do you do if you only have the one server?

Hi,
Just additional. Please also refer to following threads and article, then check if can help you.
Migrate
SBS 2003 to Windows Server 2012 Standard
Migration
SBS 2003 to Windows Server 2012 Standard
Transition
from Small Business Server to Standard Windows Server
Hope this helps.
Best regards,
Justin Gu

Chat feature for Microsoft Exchange 2013

Hi Good day,
is there any way to have a simple chat feature service for exchange 2013? im looking for some solutions but only Exchange 2000 has this common feature. I just need to have a simple chat service for our internal and branch offices

Hi,
There is no feature in Exchange server 2013 to meet your requirement. But we can use Microsoft Lync to chat with your domain environment. Microsoft Lync is an enterprise-ready unified communications platform.
By integrating Lync Server and Exchange Server, we can also chat directly in OWA. For more information about it, we can refer to:
http://office.microsoft.com/en-001/lync/lync-server-2013-features-video-conferencing-and-instant-messaging-FX103789592.aspx
If you don’t want to deploy a Lync server in your environment, we can also use
Skype with a Microsoft account or Skype account to chat with others.
Thanks,
Winnie Liang
TechNet Community Support

Changing AD Domain name with Microsoft Exchange 2013

Hello everyone,
we need to change our Active Directory Domain name from .local to another naming convention.
We are running a Windows Server 2012 R2 environment with Exchange 2013.
- Domain Controller
- File Server
- Exchange 2013
Running on a VMware ESX Host.
What is the applied way to change the Domain name? Or is there no way to change in the running Forest and we have to re-setup everything?
Thank you for your answers.
Regards,
Sebastian

Hello,
You need install new Exchange server in your new enviroment (forest).
Please read this link:
Prepare mailboxes for cross-forest moves using the Prepare-MoveRequest.ps1 script in the Shell
Other nice article:
Moving to a new forest and retaining the same SMTP domain ( with native scripts ) -
Part I
Regards

Microsoft Exchange 2013 eDiscovery - specific search query: looking for specific hyperlinks within e-mails content/body

Dear all:
I am currently using the MS Exchange 2013 eDiscovery feature with the objective to identify which of my users have received emails containing specific hyperlinks (e.g. http://website1/webroot/file.zip, http://website2/webroot/file.zip, etc.) from an unknown
sender.
To this end, I have been creating an eDiscovery on-hold case looking for a specific search criteria in all mailboxes.
As the search criteria, I have tried many options but was unable to obtain satisfying results: I know I am missing some e-mails from this specific search (I checked manually). I have notably tried the following search queries (with and without the body:
search operator, with and without double quotes, etc.)
body:http://website1/* OR body:http://website2/*
body:"http://website1/*" OR body:"http://website2/*"
body:"website1*" OR body:"website2*"
body:"*website1*" OR body:"*website2*"
When replaying these queries on my local Outlook client, everything works fine and I get results as expected.
However, when going through the ECP eDiscovery feature, I am missing some results.
Therefore, I am looking for any advice on what Exchange eDiscovery KQL query I should use to identify all emails containing, in their message body, a list of specific hyperlinks/URLs.
Many thanks in advance for your help.
S.

Alas I do not know the answer to resolution via ECP and like you I have found it to be a bit maddening to use ECP for discovery tests Ive done when comparing results with our DigiScope product. I know we can accomplish what your looking to do via Regular
Expression but again that's with a 3rd party tool.
One thought is I suppose it could be an indexing issue with the DB, so perhaps rebuilding the index would help?
If you do get it working I would love to know the resolution since many of my tests with ECP have left me yelling at the screen. When its works its cool when not well...
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003
--> 2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Livecycle ES4 and Microsoft Exchange 2013

Hi,
My customer inquired me of configuring LiveCycle ES4 with Microsoft Exhange 2013 but supported documentation says that LiveCycle only supports Microsoft Exhange 2010 and earlier. ¿Could be posible LiveCycle ES4 SP1 either supports Microsoft Exhange 2013 or configure an account in Microsoft Exhange 2013 for configuring in Livecycle without getting on troubles?
Thanks in advance.

MS Office 2013 is also not supported with ES4 SP1.
Here is the link to updated documentation - http://helpx.adobe.com/livecycle/help/livecycle-es4-supported-platforms.html#Software support for PDF Generator
Regards,
Varun

Exchange 2013 DNS Records

i have 3 domain and 1 Exchange Server for this 3 domain, so can some one guide me how i can configure DNS internal and External?
Root Domain :
contoso.com
Sub Domain :
contoso1.com
contoso2.com
and also if you have document to how configure Autodiscovery for this all domain?
Regards,

Hi ,
Based on my knowledge we need to configure the split dns for your scenario.Because most of the active directory domain name and external domain wouldn't be same in lot of cases.
Reference Link : http://www.msexchange.org/articles-tutorials/exchange-server-2010/mobility-client-access/using-pinpoint-dns-zones-exchange-2010.html
Root Domain :
contoso.com - primary smtp address suffix would be - @public1.com
Sub Domain :
contoso1.com - primary smtp address suffix would be - @public2.com
contoso2.com - primary smtp address suffix would be - @public3.com
On such case you need to create a zone on internal active directory DNS for any one of the suffixes (public1.com,public2.com,public3.com).
Note : That forward look up zone creation in active directory is based upon the names that you are going to use for exchange url's ,outlook anywhere names and autodiscover .Because those names used on exchange should have to be resolved
internally as well externally.
In external world you need to create three autodiscover records which should be like below.
[email protected]
[email protected]
[email protected]
Most importantly you need to have the names utilized in exchange should have to be available in SAN certificate.
Note : I have given some suggestions based on my knowledge anyhow we will wait for some exchange experts to review the given info and also to get more info on this query.
Thanks & Regards S.Nithyanandham

2012 r2 -Microsoft Exchange 2013 DNS timed out

Similar Messages

Maybe you are looking for