Update website/content/docs/release-notes/consul/v1_19_x.mdx

Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
hashicorp · Jun 13, 2024 · fbdf04d · fbdf04d
1 parent 23c423e
commit fbdf04d
Showing 1 changed file with 5 additions and 6 deletions.
diff --git a/website/content/docs/release-notes/consul/v1_19_x.mdx b/website/content/docs/release-notes/consul/v1_19_x.mdx
@@ -35,12 +35,11 @@ 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 specified with a Service Address (vs. only a Node Address), return the hostname instead of the `.addr` address.
-    This results in ambiguous answers where multiple service instances return the same hostname. 
-    It is impossible to resolve the individual service addresses.
-    This can affect Nomad installations, where the Service Address field is always specified to Consul.
-    Setting `experiments: [ "v1dns" ]` in the agent configuration will revert to the old behavior.
-    A fix will be present in a future release of Consul 1.19.1 [[GH-21325](https://github.com/hashicorp/consul/issues/21325)].
+- 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