locked
Issue with FQDN resolution on Dynamics CRM site RRS feed

  • Question

  • I am having an issue where the FQDN for the Dynamics CRM site is not working where the non-FQDN is. I am setting up CRM to be used as an IFD, and the CRM address is going to be the same FQDN for both internal and external use and is formatted in the following way:

    CRM.Company.com

    I have setup CRM to run off of this address for all of the addresses (Web application, organization web service, discovery web service, and deployment web service) in the deployment manager, changed the binding type to HTTPS, assigned the binding for port 444, set that binding in IIS with a certificate that is only for the above address format, and so internally when I am trying to access the company site, I use this address:

    https://crm.company.com:444/company

    I am not able to get to the company page from either the local server browser or from my desktop (which is in the same subnet). However, on the server browser, I am able to get to the company web site using this address:

    https://crm:444/company

    To try and verify if it were a DNS issue, I created the ADFS site in the same way (created an alias for the site to the server), then navigated to the federation metadata successfully from my desktop using the following address:

    https://adfs.company.com/federationmetadata/2007-06/federationmetadata.xml

    Thus, I am not thinking that it is a DNS issue since this worked fine and the only difference between the two DNS aliases is that one is ADFS and one is CRM and the CRM uses a port. I have been working on the issue for a bit and now have come to the point where I cannot think of anything else to do here and would greatly appreciate any guidance anyone can give me.

    Saturday, August 25, 2012 4:55 AM

All replies

  • HI JeffBothel,

                    I think your problem is that you need to use a different url when IFD is set something like

    https://company.crm.company.com:444 , and be sure you have a DNS entry pointing to the CRM server for company.crm.company.com.


    Regards,
    Damian Sinay

    Saturday, August 25, 2012 7:05 AM
  • I think I should clarify, right now I am trying to get claims based authentication internally to work, and internally the address CRM.Company.com:444/Company is not resolving where CRM:444/company is, and so I am trying to tackle that issue first, and then second I am trying to get the claims based authentication working, which is not seeing the ADFS that is installed on the same server just with a different name to access this functionality and is at the URL adfs.company.com
    Saturday, August 25, 2012 2:16 PM