Getting this in services-messages.log.

I stupidly added the same cname entry in "Additional DNS Names" for two primaries. I have removed that, but the config location still has the wrong info. But of course, there is no guarantee this caused the problem.

any idea how to get the server to recompute the config location again.

I added a new primary server in the hope that that would trigger it (i needed it for Reporting anyway), but it hasn't done so.

there is a field called "RECOMPUTE" in the table "ZLOCATIONCONFIGRESPONSE" which is zero in DEV and PROD. will turning this to one do anything ?

also in DEV there are two row in the table "ZLOCATIONCONFIGRESPONSE" but prod only has one.