vincent/homelab
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

style: fix markdown
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
vincent 2023-11-01 19:53:42 +01:00
parent db8b2c3b1e
commit b54420c0d9
3 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -22,7 +22,6 @@ make create-dev
## Rebuild
## Architecture
```mermaid

2
docs/ADR/004-DNS.md
View File

@ -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

2
docs/Concepts/DNS.md
View File

@ -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