We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CName for the storage db in production is not registered in DNS and should be so.
For Storage in production the connection string now holds the actual hostname of the server instead of the CNAME.
The text was updated successfully, but these errors were encountered:
@ootneim Is this a quick fix? Maybe already done?
Sorry, something went wrong.
Looks like the CNAME is incorrect in DNS.
storage-postgres.altinn.no -> altinn-storage-db-pgflex.postgres.database.azure.com
Correct setting is: storage-postgres.altinn.no -> altinn-storage-db-prod-pgflex.postgres.database.azure.com
@bengtfredh or @Herskis have access to update the DNS record.
@ootneim CNAME is updated - record has TTL 2h - but can take up to 24 hour for all dns to be updated
Using CName in settings for Storage. Will be rolled out to production with Release 743
SandGrainOne
No branches or pull requests
Description
CName for the storage db in production is not registered in DNS and should be so.
Additional Information
For Storage in production the connection string now holds the actual hostname of the server instead of the CNAME.
Tasks
Acceptance Criterias
The text was updated successfully, but these errors were encountered: