From ec14b03d8594ebf967d910e7416facfcef36fe75 Mon Sep 17 00:00:00 2001 From: Yegor S Date: Tue, 2 Jan 2024 12:30:52 -0500 Subject: [PATCH] Updated Example Configurations (markdown) --- Example-Configurations.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Example-Configurations.md b/Example-Configurations.md index 5abc7fd..eddacde 100644 --- a/Example-Configurations.md +++ b/Example-Configurations.md @@ -47,6 +47,7 @@ Let's get a bit fancier, and specify multiple upstreams and route requests via ` - Define 2 networks with 2 different subnets: `192.168.1.0/24` and `192.168.100.0/24` - Define 2 upstreams with different levels of blocking - Using a network policy map `192.168.1.0/24` to `upstream.0` and `192.168.100.0/24` to `upstream.1`. This means that requests originating from each subnet will be sent to a different upstream DNS resolver += A DNS query from a device with MAC address 14:54:4a:8e:08:2d from any subnet would be sent to upstream.1 (since MAC rules match 2nd). - If a request doesn't match the defined networks, it will use the default `upstream.0`. To override this behavior and REFUSE queries from undefined networks, use [restricted resolver](https://github.com/Control-D-Inc/ctrld/blob/main/docs/config.md#restricted) config param. ``` @@ -62,6 +63,10 @@ Let's get a bit fancier, and specify multiple upstreams and route requests via ` { 'network.1' = ['upstream.1']} ] + macs = [ + {"14:54:4a:8e:08:2d" = ["upstream.1"]} + ] + [network] [network.0] name = 'Adults'