Thanks, the way I have it right now is each discrete network has a dnsdist
frontend, so that the source network activates bind views. Looks like I'll set
up a pdns backend with several pdns processes (I need 17) running on different
ports. This will hold me over and I can start the full
Dnsdist would always need an authoritative server to server domains (note that
you can distill dns replies in dnsdist, it really shouldn't be used for your
use case).
The backend doesn't need to be PowerDNS: dnsdist is just used to send traffic
to a different backend based on the parameters
Thanks, that does help, but I was hoping I could do it all in dnsdist w/o
implementing a pdns backend yet.
-Original Message-
From: Frank Louwers
Sent: Friday, May 10, 2024 4:31 PM
To: Rory Toma ; dnsdist mailing list
Subject: Re: [dnsdist] Question about local override
CAUTION:
My current setup uses dns views (which I abhor).>
So, depending on the subnet the request comes from, certain domains
get different answers.
I'd like to use dnsdist, but I'm having difficulty in implementing
domain overrides, and I haven't been able to find a good, clean
example.
So
