From 711fe1d806e25163f7e2d7f210a4999c7910c9a2 Mon Sep 17 00:00:00 2001 From: Christian Heusel Date: Sat, 31 Dec 2022 12:20:12 +0100 Subject: [PATCH] enumerate the config --- docs/dns-records.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/dns-records.md b/docs/dns-records.md index 530590bc..3dbe85e6 100644 --- a/docs/dns-records.md +++ b/docs/dns-records.md @@ -7,7 +7,7 @@ An example usecase is to serve apps on the same host via a reverse proxy like NG ## Setup -### Change the configuration +### 1. Change the configuration 1. Change the `config.yaml` to contain the desired records like so: @@ -25,11 +25,11 @@ dns_config: ... ``` -Restart your headscale instance. +2. Restart your headscale instance. Beware of the limitations listed later on! -### Verify that the records are set +### 2. Verify that the records are set You can use a DNS querying tool of your choice on one of your hosts to verify that your newly set records are actually available in MagicDNS, here we used [`dig`](https://man.archlinux.org/man/dig.1.en): @@ -56,7 +56,7 @@ grafana.myvpn.example.com. 593 IN A 100.64.0.3 ;; MSG SIZE rcvd: 66 ``` -### Optional: Setup the reverse proxy +### 3. Optional: Setup the reverse proxy The motivating example here was to be able to access internal monitoring services on the same host without specifying a port: