localstack · HarshCasper · Jul 24, 2023 · Jun 9, 2023
diff --git a/content/en/references/configuration.md b/content/en/references/configuration.md
@@ -197,7 +197,7 @@ The old lambda provider is temporarily available in Localstack&nbsp;v2 using `PR
 | `BUCKET_MARKER_LOCAL` | `__local__` (default) | Optional bucket name for running lambdas locally.<br> **Still supported in new provider but default changed to `hot-reload`.** |
 | `LAMBDA_CODE_EXTRACT_TIME` | `25` (default) | Time in seconds to wait at max while extracting Lambda code. By default, it is 25 seconds for limiting the execution time to avoid client/network timeout issues. <br> **Removed in new provider because function creation happens asynchronously.**|
 | `LAMBDA_DOCKER_NETWORK` | | Optional Docker network for the container running your lambda function. This configuration value also applies to ECS containers. Needs to be set to the network the LocalStack container is connected to.<br> **Still supported in new provider.** |
-| `LAMBDA_DOCKER_DNS` | | Optional DNS server for the container running your lambda function.<br> **Currently not supported in new provider.** |
+| `LAMBDA_DOCKER_DNS` | | Optional DNS server for the container running your lambda function.<br> **Supported in new provider since LocalStack 2.2.** |
 | `LAMBDA_DOCKER_FLAGS` | `-e KEY=VALUE`, `-v host:container`, `-p host:container`, `--add-host domain:ip` | Additional flags passed to Docker `run`\|`create` commands. Supports environment variables, ports, volume mounts, extra hosts, networks, labels, user, platform and privileged mode.<br> **Still supported in new provider.** |
 | `LAMBDA_CONTAINER_REGISTRY` | `lambci/lambda` (default) | An alternative docker registry from where to pull lambda execution containers.<br> **Replaced by `LAMBDA_RUNTIME_IMAGE_MAPPING` in new provider.** |
 | `LAMBDA_REMOVE_CONTAINERS` | `1` (default) | Whether to remove any Lambda Docker containers. Only applicable when using docker-reuse executor.<br> **Still supported in new provider.** |

@@ -198,7 +198,7 @@ The following configuration options from the old provider are discontinued in th
 * The `LAMBDA_STAY_OPEN_MODE` is now the default behavior and can be removed. Instead, use the `LAMBDA_KEEPALIVE_MS` option to configure how long containers should be kept running in between invocations.
 * The `LAMBDA_REMOTE_DOCKER` option is not used anymore since the new provider automatically copies zip files and configures hot reloading.
 * The `LAMBDA_CODE_EXTRACT_TIME` option is no longer used because function creation is now asynchronous.
-* The `LAMBDA_DOCKER_DNS`, `HOSTNAME_FROM_LAMBDA`, `LAMBDA_FALLBACK_URL`, `SYNCHRONOUS_KINESIS_EVENTS`, `SYNCHRONOUS_SNS_EVENTS` and `LAMBDA_FORWARD_URL` options are currently not supported.
+* The `HOSTNAME_FROM_LAMBDA`, `LAMBDA_FALLBACK_URL`, `SYNCHRONOUS_KINESIS_EVENTS`, `SYNCHRONOUS_SNS_EVENTS` and `LAMBDA_FORWARD_URL` options are currently not supported.
 * The `LAMBDA_CONTAINER_REGISTRY` option is not used anymore. Instead, use the more flexible `LAMBDA_RUNTIME_IMAGE_MAPPING` option to customize individual runtimes.
 * The `LAMBDA_XRAY_INIT` option is no longer needed because the X-Ray daemon is always initialized.
 
@@ -209,6 +209,7 @@ However, the new provider still supports the following configuration options:
 * The `LAMBDA_DOCKER_NETWORK` option.
 * The `LAMBDA_DOCKER_FLAGS` option.
 * The `LAMBDA_REMOVE_CONTAINERS` option.
+* The `LAMBDA_DOCKER_DNS` option since LocalStack 2.2.
 
 ## Examples