luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Backport of Fix code block examples on dns-static-lookups.mdx into release/1.16.x (#18894) 

Fix code block examples on dns-static-lookups.mdx

HCL and JSON configuration examples were being displayed in the same
code block. This commit separates the configurations to properly
display them as independent configuration examples.

Co-authored-by: Blake Covarrubias <blake@covarrubi.as>
This commit is contained in:
hc-github-team-consul-core 2023-09-19 14:08:09 -04:00 committed by GitHub
parent 8b422451e2
commit 2d26ebc264
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
website/content/docs/services/discovery/dns-static-lookups.mdx
View File

@ -234,11 +234,13 @@ _redis._tcp.service.phx1.peer.consul. 0 IN SRV 1 1 29142 0a010d56.addr.consul.
If a service registered with Consul is configured with an explicit IP address or addresses in the [`address`](/consul/docs/services/configuration/services-configuration-reference#address) or [`tagged_address`](/consul/docs/services/configuration/services-configuration-reference#tagged_address) parameter, then Consul returns the hostname in the target field of the answer section for the DNS SRV query according to the following format: If a service registered with Consul is configured with an explicit IP address or addresses in the [`address`](/consul/docs/services/configuration/services-configuration-reference#address) or [`tagged_address`](/consul/docs/services/configuration/services-configuration-reference#tagged_address) parameter, then Consul returns the hostname in the target field of the answer section for the DNS SRV query according to the following format:
```text ```text
<hexadecimal-encoded IP>.addr.<datacenter>.consul`. <hexadecimal-encoded IP>.addr.<datacenter>.consul.
``` ```
In the following example, the `rabbitmq` service is registered with an explicit IPv4 address of `192.0.2.10`. In the following example, the `rabbitmq` service is registered with an explicit IPv4 address of `192.0.2.10`.
<CodeTabs>
```hcl ```hcl
node_name = "node1" node_name = "node1"
@ -247,6 +249,9 @@ services {
address = "192.0.2.10" address = "192.0.2.10"
port = 5672 port = 5672
} }
```
```json
{ {
"node_name": "node1", "node_name": "node1",
"services": [ "services": [
@ -259,6 +264,8 @@ services {
} }
``` ```
</CodeTabs>
The following example SRV query response contains a single record with a hostname written as a hexadecimal value: The following example SRV query response contains a single record with a hostname written as a hexadecimal value:
```shell-session ```shell-session
@ -275,6 +282,8 @@ $ echo -n "c000020a" | perl -ne 'printf("%vd\n", pack("H*", $_))'
In the following example, the `rabbitmq` service is registered with an explicit IPv6 address of `2001:db8:1:2:cafe::1337`. In the following example, the `rabbitmq` service is registered with an explicit IPv6 address of `2001:db8:1:2:cafe::1337`.
<CodeTabs>
```hcl ```hcl
node_name = "node1" node_name = "node1"
@ -283,6 +292,9 @@ services {
address = "2001:db8:1:2:cafe::1337" address = "2001:db8:1:2:cafe::1337"
port = 5672 port = 5672
} }
```
```json
{ {
"node_name": "node1", "node_name": "node1",
"services": [ "services": [
@ -295,6 +307,8 @@ services {
} }
``` ```
</CodeTabs>
The following example SRV query response contains a single record with a hostname written as a hexadecimal value: The following example SRV query response contains a single record with a hostname written as a hexadecimal value:
```shell-session ```shell-session