From 09538e62b128ab063f0dc27ffeb2e94bcd77f470 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Fri, 14 Jun 2024 08:56:03 -0700 Subject: [PATCH] Backport of docs: known issue with v2dns SRV requests into release/1.19.x (#21340) * backport of commit 23c423e6e3c9e98113f696097f651b8149113470 * backport of commit fbdf04dfdeb9d9ff92417ecae11b4cc232b40a10 --------- Co-authored-by: DanStough --- website/content/docs/release-notes/consul/v1_19_x.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/content/docs/release-notes/consul/v1_19_x.mdx b/website/content/docs/release-notes/consul/v1_19_x.mdx index fe373eed73f3..aa6b6f57ab0b 100644 --- a/website/content/docs/release-notes/consul/v1_19_x.mdx +++ b/website/content/docs/release-notes/consul/v1_19_x.mdx @@ -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.