> use DNSStubListenerExtra=
It's indeed this directive I'm using on the downstream interface. Maybe
I should have mentioned that.
Configuration / results (MACs etc. obfuscated, but all correct on the
running system):
# head -n-0 /etc/systemd/network/linux-dummy_local0.{netdev,network}
==>
On Mon, May 9, 2022, 16:35 Peter Mattern wrote:
> Hi, Petr.
>
> > Do you need any systemd-resolved specific features?
> Primarily, it's about the way directive Domains allows for directing
> queries to particular DNS servers based on the queries' domains.
> I'm using it to restrict the ISP's
Hi, Petr.
> Do you need any systemd-resolved specific features?
Primarily, it's about the way directive Domains allows for directing
queries to particular DNS servers based on the queries' domains.
I'm using it to restrict the ISP's DNS server to the ISP's domain, use a
local DNS server for
On Mo, 09.05.22 15:32, Lennart Poettering (lenn...@poettering.net) wrote:
> On So, 08.05.22 15:00, Peter Mattern (pmatt...@arcor.de) wrote:
>
> > Hello.
> >
> > Apparently resolved is ignoring DNS servers which are listening on Linux
> > dummy interfaces.
>
> It should not do that. Are you sure
On So, 08.05.22 15:00, Peter Mattern (pmatt...@arcor.de) wrote:
> Hello.
>
> Apparently resolved is ignoring DNS servers which are listening on Linux
> dummy interfaces.
It should not do that. Are you sure you configured the interfaces
properly, and they are up?
Provide "networkctl status"
Hi Peter,
is there a reason why do you want resolved to serve whole LAN? It has
its problems and I think its authors meant it as localhost cache. I
don't think resolved considers it common to have more than one DNS
server on the localhost.
Is there a reason why you wouldn't use dnsmasq, unbound
