Skip to content

Commit

Permalink
Backport of docs: known issue with v2dns SRV requests into release/1.…
Browse files Browse the repository at this point in the history
…19.x (#21340)

* backport of commit 23c423e

* backport of commit fbdf04d

---------

Co-authored-by: DanStough <dan.stough@hashicorp.com>
  • Loading branch information
hc-github-team-consul-core and DanStough authored Jun 14, 2024
1 parent 3296038 commit 09538e6
Showing 1 changed file with 6 additions and 0 deletions.
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

0 comments on commit 09538e6

Please sign in to comment.