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

docs: known issue with v2dns SRV requests #21331

Merged
merged 2 commits into from
Jun 14, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions website/content/docs/release-notes/consul/v1_19_x.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,12 @@ For more detailed information, please refer to the [upgrade details page](/consu

The following issues are known to exist in the v1.19.x releases:

- v1.19.0 - DNS SRV records for registrations that specify a service address instead of a node address return identical `.service` hostnames instead of unique `.addr` addresses.
As a result, it is impossible to resolve the individual service addresses.
This bug can affect Nomad installations using Consul for service discovery because the service address field is always specified to Consul.
To revert to the old DNS behavior, set `experiments: [ "v1dns" ]` in the agent configuration.
We plan to include a fix in a future release of Consul v1.19.1 [[GH-21325](https://github.com/hashicorp/consul/issues/21325)].

## Changelogs

The changelogs for this major release version and any maintenance versions are listed below.
Expand Down
Loading