Hi all,

I've got a CRM 4 internet facing deployment that's having trouble verifying
the dns entry. When I use the "Check DNS" function, it seems to be omitting
the organization name from the string. I am expecting to see
"organization.domain.org" but instead it says it can't resolve "domain.org"
.... If I manually put in the organization name in the IFD App Root Domain
(just as an experiment), it doubles up and says it can't resolve
"organization.organization.domain.org". The organization.domain.org address
exists on the internet, it just isn't connecting to CRM. The only difference
between this implementation and others I've done is that the CRM server in
this particular setup is sitting in a DMZ.

Any suggestions?

Thanks,

Rob

Hi Rob:

I had the same problem. This is due to how it was installed and
organization was selected. When using the IFDP it will add your organization
name to the name that was used during the installation. So for example
during installation you entered the name crm.mycompany.com when using the crm
IFDP tool and you still want to use the organization crm you will find it
will do crm.crm.mycompany.com and this is what you will need DNS to point to.


Since I played with the instalaltion several times before I deployed this I
fixed it for deployment. What I did was during installation I chose a name
for internal DNS only for example remote.mycompany.com, then I used the
configuraiton wizard to add a new organization for the actual DNS name used
externaly i.e. crm.mycompany.com then I set this for the default. Now, use
the IFD tool and setup the IIS service to respond to CRM.MYCOMPANY.COM and it
should work.

Now, internaly you will still use http://machinename:5555 and it will
redirect you to the correct organization name.

I hope this helps or points you in the right direction.

Best regards,

Jason


"Rob Landolt" wrote: