Skip to content
New issue

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

azure private dns txt needs ttl #823

Merged
merged 1 commit into from
Mar 6, 2025
Merged

azure private dns txt needs ttl #823

merged 1 commit into from
Mar 6, 2025

Conversation

boylec
Copy link
Contributor

@boylec boylec commented Mar 6, 2025

Azure private DNS TXT record creation is returning a 400. After debugging, I've deduced that it is because no TTL is being provided. This commit introduces a default TTL of 3600 seconds.

@shibayan shibayan requested review from Copilot and shibayan March 6, 2025 04:59

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Overview

This PR addresses a 400 error encountered during Azure private DNS TXT record creation by setting a default TTL value.

  • Adds a default TTL of 3600 seconds when creating the TXT record data.

Reviewed Changes

File Description
KeyVault.Acmebot/Providers/AzurePrivateDnsProvider.cs Sets a default TTL value to fix the 400 error during TXT record creation

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

KeyVault.Acmebot/Providers/AzurePrivateDnsProvider.cs:48

  • [nitpick] Consider using a named constant for the default TTL value (e.g. DEFAULT_TTL) to improve clarity and maintainability.
var txtRecordData = new PrivateDnsTxtRecordData() { TtlInSeconds = 3600 };
Copy link
Owner

@shibayan shibayan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@shibayan shibayan merged commit a9d5cd5 into shibayan:master Mar 6, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants