You’re offline. This is a read only version of the page.
140
Dear Microsoft Dynamics Community,
Actually I’m about to configure Microsoft Dynamics CRM 2011, for internet facing deployment i was able to do so in a test environment now that i will start doing it in a production environment I have
some doubts about the DNS configuration required for my environment :
In our environment we host both internal ( windows 2008 r2 DNS)and external (not windows DNS) DNS.
I also have an SSL ip for My Dynamics CRM 2011 server;
I want to know if the configuration i have in mind is correct My DNS configuration will be as below :
· External access used to access Microsoft Dynamics (IFD): crm.test.net ( add a DNS record for livecrm that point the IP address of the CRM live in both internal and external DNS). Should i use the Public or the private IP address
· Microsoft Dynamics CRM discovery web service crmdev.test.net ( add a DNS record for crmdev that point the IP address of the CRM live in the internal DNS). Should i use the Public or the private IP address
· AD FS 2.0 server crmsts.test.net (add a DNS record for crmsts that point the IP address of the ADFS server in the internal DNS). Shoud i use the Public or the private IP address
· Microsoft Dynamics CRM internet facing deployment crmauth.test.net ( add a DNS record for auth that point the IP address of the CRM live in the internal DNS). Should i use the Public or the private IP address
A short description of my MS dynamics CRM environment Schema :
· I have an active directory domain service server that host the internal DNS.
· Ms Dynamics CRM 2011 server with SQL server 2008 R2 installed.
· and Finlay STS provider it’s a windows 2008 r2 with ADFS 2.0 installed.
I really need your help please let me know if I should clarify something else about my environment.
Hope to hear from you soon.
Best regards,
Adnane EL MAJDOULI
*This post is locked for comments
I have the same question (0)
Hi Adnane,
For internal users who would acess CRM using the IFD address or internal claims address, it's typically a best practice to use A records in the forward lookup zone to point back to the internal IP of their corresponding host record in the default zone (if you were going from an internal .local domain to an external .com domain, for example).
For external access, you will need to supply the public IP address for the external DNS entries.
You can read more about how to implement this in the following MSDN article:
msdn.microsoft.com/.../gg188591.aspx
Thank you,
Derek
Share
Report
All responses (
Answers (
