Hi all,
thank you for flagging this issue.
Its root cause was an infrastructure hiccup we experienced on July 11. Due to this issue, a new location database was generated, and the correspondent DNS record updated accordingly, but it could not be uploaded to the file server.
Thus, the libloc updater compared the DNS request content with the latest database version available from the HTTPS server - which was dated July 10. Therefore, updating was refused.
Since @ms resolved the infrastructure issue early on July 12, you should now all see location database updates working fine again. No manual interaction is required whatsoever, as the updater will periodically retry to fetch an up-to-date database itself.
I will update bug #12901 accordingly, and close it as being fixed.
Apologies for the inconvenience, and best regards,
Peter Müller