Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #245015 > unrolled thread
| Started by | Kamil Jońca <kjonca@o2.pl> |
|---|---|
| First post | 2022-02-05 12:40 +0100 |
| Last post | 2022-02-05 12:40 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: interface/network scripting - how to? Kamil Jońca <kjonca@o2.pl> - 2022-02-05 12:40 +0100
| From | Kamil Jońca <kjonca@o2.pl> |
|---|---|
| Date | 2022-02-05 12:40 +0100 |
| Subject | Re: interface/network scripting - how to? |
| Message-ID | <DNrA6-3ZR-11@gated-at.bofh.it> |
Anssi Saari <as@sci.fi> writes: > Kamil Jońca <kjonca@o2.pl> writes: > >> 2. name resolving is properly configured: >> ie. home1.tld DNS queries are passed to home1 network >> work1.tld DNS queries are passed to work1 network (via openvpn tunnel) >> work2.tld DNS queries are passed to work2 network (via ipsec tunnel) > > So how have you setup this part? I always thought this needs a local > name server, such as systemd-networkd provides and which I switched to > once I heard it had been implemented. Before I had just wobbly > resolvconf which usually got the DNS setup wrong. I managed fix it so it > was mostly OK but it was never good. Point for you. :) I forgot to mention about dnsmasq, whose configuration is updated by scripts. KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Back to top | Article view | linux.debian.user
csiph-web