Add information about our DNS server

localstack · Sep 28, 2023 · 0f84a3b · 0f84a3b
1 parent d417788
commit 0f84a3b
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/.../en/references/network-troubleshooting/transparent-endpoint-injection/_index.md b/.../en/references/network-troubleshooting/transparent-endpoint-injection/_index.md
@@ -13,6 +13,12 @@ Suppose you're attempting to access LocalStack, but you're relying on transparen
 {{< figure src="../images/2.svg" width="400" >}}
 
 If you're using LocalStack with an [API key]({{<ref "getting-started/api-key">}}), then you can utilize the [DNS server]({{<ref "user-guide/tools/transparent-endpoint-injection/dns-server">}}) to perform requests to LocalStack as if it were AWS.
+You need to make two changes:
+
+* Publish port 53 from the LocalStack docker container to your host.
+* Configure your host to use the LocalStack DNS server by default.
+
+For more details, see your [DNS server documentation]({{<ref "user-guide/tools/transparent-endpoint-injection/dns-server">}}).
 
 For the community edition of LocalStack, you can employ your own DNS server to achieve a similar outcome, but it won't be managed by LocalStack. Note that in both cases, SSL verification must be disabled. See the [limitations of the DNS server]({{<ref "user-guide/tools/transparent-endpoint-injection/dns-server#limitations" >}}) for more information.