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
Copy file name to clipboardExpand all lines: docs/configuration.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,3 +38,18 @@ HTTPS verification can be disabled by setting environment variable `OMADA_DISABL
38
38
39
39
An option to keep HTTPS verification enabled is to create a public DNS A record pointing to your controllers private IP address.
40
40
41
+
## Custom DNS records
42
+
43
+
It is possible to create a dummy DHCP reservation in the Omada controller to create custom DNS records.
44
+
45
+
* In the Omada controller go to `Settings` -> `Services` -> `DHCP Reservations`
46
+
* Create a new DHCP reservation:
47
+
- Enter a dummy MAC address e.g AA-AA-AA-AA-AA-AA
48
+
- Enter the desired IP address
49
+
- Enter the client name
50
+
- (If you are unable to set the client name then use the description - there is a fallback in the code for this and the options seem to vary across controller versions)
51
+
Example:
52
+
53
+

54
+
55
+
Note that wildcard records are supported by setting the client name to `*` or `*.subdomain`
0 commit comments