In some cases, despite an apparently correctly performed configuration, it has been reported that the domain search does not work – more precisely: the DomainIndexer task did not perform any indexing of the intended databases. In the "Domain Indexer Status" views of the CATALOG.NSF database, there were also no documents that would normally log the execution of the indexing.
My observations on domain search
With a CATALOG.NSF database that already existed before the domain was set up, activating the domain search has NEVER worked for me.
Only when you delete the existing CATALOG.NSF and (of course, activate the domain search first, restart the server if necessary) then have it recreated via LOAD CATALOG, did it work without problems.
Interesting side effect
The normal database catalog has the DB title "Catalog (6)", for example. When the domain search has been activated and you recreate the database using LOAD CATALOG, it has a different title, e.g.: "Domain Catalog".
I suspect that when the DB is created – if the domain search has been activated – it internally receives a special flag – and then the Domain Indexer and subsequently the search work correctly…
In addition, you will notice that the ACL of the newly created CATALOG.NSF automatically receives a group entry "Domain Catalog Servers" (depending on the version used, this group is also automatically created in the NAMES.NSF on the Domino server).
With some version 5 installations, however, the group was set to the ACL access level Reader – replication with other servers then did not work. Manually deleting the group did nothing – the group was automatically added again with Reader rights. I then always explicitly entered all servers into the ACL – after that, replication worked as well…