smad/org-roam
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

brain initiation

Browse Source
This commit is contained in:
smad
2025-11-05 09:18:11 +01:00
commit 933aa8a985
191 changed files with 6203 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
20230607132948-dns.org Normal file
View File

@@ -0,0 +1,23 @@
:PROPERTIES:
:ID: 80666401-173e-4828-9c29-552dab716946
:END:
#+title: dns
#+filetags: :network:basics:
dynamic naming service that transforms [[id:f055acfb-05dd-4228-a92a-356240b8c975][IP]] addresses into human readable form. can be used to give [[id:f2b1d5af-1a7d-47a5-95c8-4a85d558419e][server]] domain names (A-entry) or to giver domain names an alias (Cname-entry).
* How To change the local resolving dns server
If the pc changes the network interface (e.g. when connecting/disconnecting from wireguard subet) the network manager checks for the corresponding dns server. The usual server responsible for that is the networking router (ftitzbox 192.168.178.1). In the case of an internal server running the local dns this is not the case, because the Fritzbox does not have the corresponding dns entries for the local network. To change this behaviour one could change the [[id:daa194c9-63f1-433e-8826-a0b4e9020e16][wireguard]] DNS Setting in ~/etc/wireguard/w1.conf~ for every peer that needs the new dns. If the dns should not be dependent on the wireguard connection ( relevance for [[id:408e8348-778a-4fbd-a14d-9f3d9c595b4a][cluster]] server in local networks) the ~resolve.conf~ file should be changed to the local dns server. For that you must:
** alter the file
Change ther file to look for the local dnbs server. ([[id:673d1cb1-536b-42f1-a046-40a8937c4283][root]] priv. needed ([[id:dc54334e-afa9-4a53-be91-1e90bc6bf8d0][sudo]])
#+begin_src bash
sudo nano /etc/resolv.conf
#+end_src
To include the ~nameserver~ of your choice for example:
#+begin_src bash
nameserver 127.0.0.1
#+end_src
If the Peer has its own nameserver running, or any other IP in the local network.
NOTE: The server has to deploy the dns server on [[id:f4bb4857-2112-4e10-a22e-6da1436ce7b7][port]] 53 for that to work and the [[id:70899526-8b7d-4976-94fc-cc07c41e550a][client]] in question has to have acces to this server port.