You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| stale_record_duration | ❌ | duration | How long to keep serving stale records for clients/devices which are no longer present in the Omada controller. Specified in Go time [duration](https://pkg.go.dev/time#ParseDuration) format |
22
-
| ignore_startup_errors | ❌ | bool | ignore connection/configuration errors to the omada controller on startup. Set this to true if you want coredns to startup even if unable to connect to omada (default false)|
23
-
22
+
| ignore_startup_errors | ❌ | bool | ignore connection/configuration errors to the omada controller on startup. Set this to true if you want coredns to startup even if unable to connect to omada (default false) |
23
+
| fallthrough [ZONES...]| ❌ |[]string | Whether to enable fallthrough. If fallthrough statement is present but no zone is specified then defaults to all zones, equivilent to:<br> `fallthrough .`|
24
24
25
25
## Credentials
26
26
@@ -30,6 +30,14 @@ For this service you should create a new user in the `Admin` page of the control
30
30
31
31
A single Omada controller can support multiple network sites. This plugin can be configured to use multiple sites via the `site` configuration property (regex). Multiple sites can be specified using the `|` separator like this `SiteA|SiteB|SiteC` or all sites can be selected by setting it to `.*`
32
32
33
+
## Fallthrough behaviour
34
+
35
+
The `fallthrough` option controls the behaviour for records which are not found. If fallthrough is enabled then requests for records which are not found are passed to the next plugin in the chain. If fallthrough is disabled then records which are not found are returned an `NXDOMAIN` response by the coredns_omada plugin and processing stops without being passed down the plugin chain.
36
+
37
+
The use case for using fallthrough is to use other plugins to handle queries for the same zone as `coredns_omada` such as the [file](https://coredns.io/plugins/file/) plugin.
38
+
39
+
Note: prior to the fallthrough option being implemented, the default behaviour enabled fallthrough.
40
+
33
41
## HTTPS Verification
34
42
35
43
This will depend on your network and configuration, but due to the lack of a suitable internal DNS resolution you may need to disable HTTPS verification to the controller, as even if you have a valid certificate on your controller you need a valid DNS record pointing to your controller where coredns is running.
Copy file name to clipboardExpand all lines: docs/getting-started.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,9 @@ CoreDNS plugins need to be compiled into CoreDNS, you can follow the [build](bui
27
27
28
28
This guide provides three options on how to run CoreDNS:
29
29
30
-
-[CoreDNS binary](#coredns-binary)
31
-
-[Docker container](#docker)
32
-
-[Kubernetes](#kubernetes)
30
+
- [CoreDNS binary](#coredns-binary)
31
+
- [Docker](#docker)
32
+
- [Kubernetes](#kubernetes)
33
33
34
34
### CoreDNS binary
35
35
@@ -52,8 +52,13 @@ Note: If you do not have a valid https certificate on your controller then set t
52
52
*`OMADA_PASSWORD`
53
53
*`UPSTREAM_DNS`
54
54
55
+
The pre-built images support these optional environment variables:
56
+
*`OMADA_IGNORE_STARTUP_ERRORS` = `true` | `false`
57
+
*`FALLTHROUGH_ZONES` - defaults to all zones `.` to maintain previous compatibility. To disable fallthrough completely either set this a a fake zone (e.g `FALLTHROUGH_ZONES=disabled`) or mount a custom Corefile.
58
+
55
59
Note: If you do not have a valid https certificate on your controller then set the `OMADA_DISABLE_HTTPS_VERIFICATION` environment variable to true
0 commit comments