From 409e3a1fc696750bce6aa1c320172af3be8c208e Mon Sep 17 00:00:00 2001 From: Cuong Manh Le Date: Sat, 14 Sep 2024 22:57:12 +0700 Subject: [PATCH] Updated Example Configurations (markdown) --- Example-Configurations.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/Example-Configurations.md b/Example-Configurations.md index dc097a3..639634c 100644 --- a/Example-Configurations.md +++ b/Example-Configurations.md @@ -24,6 +24,20 @@ If you wish to route DNS queries yourself, without any magic on the part of `ctr - `ctrld service start --cd=RESOLVER_ID` - starts ctrld service in cd mode but makes no DNS routing changes - `ctrld service start --config=/path/to/ctrld.toml` - starts ctrld service in local config mode but makes no DNS routing changes +### Remember running service configuration + +Since v1.3.8, if `ctrld` has been already installed, running `ctrld start` or `ctrld service start` will start the existing `ctrld` service instead of installing new one. That means `ctrld` service will be started with last service configuration. + +Example: + +``` +$ ctrld start --cd=RESOLVER_ID -vv +$ ctrld stop +$ ctrld start # service will run with --cd=RESOLVER_ID and -vv flags. +``` + +Passing any new arguments/flags to `ctrld start` will result in old behavior. + ## Simplest The simplest possible configuration looks like this. The following config does the following: - Spawn a single DNS listener on `0.0.0.0` (all interfaces) and port `53`