Byung-Hee HWANG wrote in
<87ee13qxa1.fsf@penguin>:
...
|> First install a true local resolver such as bind9 or unbound and then
|> switch your system to use it instead of systemd-resolved. To switch to
|> bind9 you could try my
|> https://www.timedicer.co.uk/programs/help/bind9-resolved-switch.sh.php.
|>
|> [ If you want, bind9 can be set so that 'normal' lookups still go via
|> external (public) resolvers (as you specify in
|> /etc/bind/named.conf.options), but lookups for RBLs are routed
|> directly. Perhaps unbound can do the same (I haven't tried it). ]
|
|Wow it seems so difficult work! I need time to think! Thanks for your
|kind advice!! Thanks again... Dominic ^^^
On 09.05.22 16:21, Steffen Nurpmeso wrote:
I use dnsmasq for almost twenty years. On the laptop it listens
on all ip netns namespaces etc and /etc/resolv.conf is "nameserver
127.0.0.1". It locally caches but otherwise only contacts dnsmasq
on my vserv VM (via VPN address "server=192.0.2.1") where dnsmasq
sits for real. dnsmasq.conf is
dnsmasq it not a true resolver. It does DNS forwarding, which is unwanted in
case of mailservers because of DNS-based blocklists etc.
I only use non-systemd systems and have no idea of that one.
('Can understand why you would want to put everything in one, but
do not like it.)
I guess systemd-resolved does the same, just different way.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
M$ Win's are shit, do not use it !
