MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Search crawl fails when domain name matches the moss url

  Asked By: Madhavi    Date: May 17    Category: MOSS    Views: 1337

As always, hindsight is 20/20 and I'm kicking myself for not thinking of this
earlier. The situation is as follows

The windows domain that MOSS is linked too is mydomain.organization.com. The AD
is on server ad.mydomain.organization.com on This AD server also
hosts it's own DNS and all MOSS related machines are within the same AD domain.

MOSS is installed on 2 WFEs, loaded balanced to mydomain.organization.com (as
load balanced ip
mydomain.organization.com is the public facing url

All users that access this site will be from outside the domain with a public
facing DNS entry of mydomain.organization.com to

The domain and MOSS are configured for kerberos authentication.

So back to the issue, MOSS works just fine. All users external to the domain can
hit mydomain.organization.com which points to and can authenticate
without a problem.

Search, however, is not every happy. Specifically, the web crawler is configured
to crawl the website mydomain.organization.com/* and is setup for a default
access account which has the appropriate read access (i've double checked it).
The crawler fails because from the crawler's perspective,
mydomain.organization.com resolves to the Active Directory ip.

There is one more complication. The IIS websites on both WFE1 and 2 are
configured with host headers for:
mydomain.organization.com 80 (NTLM logins
mydomain.organization.com 443 (ADFS logins)
mysite.mydomain.organization.com 80/443
ssp.mydomain.organization.com 80/443

All WFEs are configured for crawling. I've tried tweaking the host files to
point mydomain.organization.com to the load balanced url on the Indexer server
only. I'm not exactly sure which server/process actually performs the crawl.

So I thinking the answer to resolve this issue would be to add an additional
alternate access url, configure the crawl to goto that url, then apply a url
translation to change it to the proper public facing url. The only concern I see
with this is that the host header my interfere with the crawl.

Has anyone else had the misfortune of having this configuration or have any
insights as to how to resolve this crawling issue?



No Answers Found. Be the First, To Post Answer.

Didn't find what you were looking for? Find more on Search crawl fails when domain name matches the moss url Or get search suggestion and latest updates.