Update DNS documentation for dns.extra_records_path

* Describe both ways to add extra DNS records
* Use "extra" instead of "custom" to align with the configuration file
* Include dns.extra_records_path in the configuration file
This commit is contained in:
Florian Preinstorfer
2024-12-16 07:07:53 +01:00
committed by nblock
parent 47b405d6c6
commit 319ce67c87
3 changed files with 66 additions and 30 deletions

View File

@@ -301,7 +301,7 @@ dns:
search_domains: []
# Extra DNS records
# so far only A-records are supported (on the tailscale side)
# so far only A and AAAA records are supported (on the tailscale side)
# See: docs/ref/dns.md
extra_records: []
# - name: "grafana.myvpn.example.com"
@@ -310,6 +310,10 @@ dns:
#
# # you can also put it in one line
# - { name: "prometheus.myvpn.example.com", type: "A", value: "100.64.0.3" }
#
# Alternatively, extra DNS records can be loaded from a JSON file.
# Headscale processes this file on each change.
# extra_records_path: /var/lib/headscale/extra-records.json
# Unix socket used for the CLI to connect without authentication
# Note: for production you will want to set this to something like: