From b54420c0d9340628ab6e2b77769c1116add162e8 Mon Sep 17 00:00:00 2001 From: vincent Date: Wed, 1 Nov 2023 19:53:42 +0100 Subject: [PATCH] style: fix markdown --- README.md | 1 - docs/ADR/004-DNS.md | 2 +- docs/Concepts/DNS.md | 2 +- 3 files changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 71f12fd..05c60ab 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,6 @@ make create-dev ## Rebuild - ## Architecture ```mermaid diff --git a/docs/ADR/004-DNS.md b/docs/ADR/004-DNS.md index 177ce9d..9c5bf44 100644 --- a/docs/ADR/004-DNS.md +++ b/docs/ADR/004-DNS.md @@ -69,7 +69,7 @@ we have curently three authority domain on NAS: we could migrate authority DNS in cluster ducamps.win and ducamps.eu are only use for application access so no dependence with cluster build need to study cluster build dependance for lan.ducamps.eu -need keepalive IP and check if no conflict if store on same machine than pihole +need keepalive IP and check if no conflict if store on same machine than pihole->ok don't need to listen on 53 only request by recursor DNS authority will dependant to storage (less problematic than recursor) ### Decision diff --git a/docs/Concepts/DNS.md b/docs/Concepts/DNS.md index 451c394..217da16 100644 --- a/docs/Concepts/DNS.md +++ b/docs/Concepts/DNS.md @@ -28,7 +28,7 @@ Pihole container in nomad cluster is set as primary DNS as add blocker secondary DNS locate on NAS manage domain *ducamps.win* on local network each recursor forward each request on *ducamps.win* to this DNS. -Each DNS forward *service.consul* request to the consul cluster. +Each DNS forward *service.consul* request to the consul cluster. Each consul node have a consul redirection in systemd-resolved to theire own consul client a DHCP service is set to do dynamic update on NAS DNS on lease delivery