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 migration to pdns at some point.
-----Original Message----- From: Frank @ kiwazo.be <frank+p...@tembo.be> Sent: Friday, May 10, 2024 5:01 PM To: Rory Toma <rory.t...@ooma.com> Cc: dnsdist mailing list <dnsdist@mailman.powerdns.com> Subject: Re: [dnsdist] Question about local override CAUTION: This email is originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. 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 you decide (eg source ip) Frank > On 10 May 2024, at 22:47, Rory Toma <rory.t...@ooma.com> wrote: > > 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 <fr...@tembo.be> > Sent: Friday, May 10, 2024 4:31 PM > To: Rory Toma <rory.t...@ooma.com>; dnsdist mailing list > <dnsdist@mailman.powerdns.com> > Subject: Re: [dnsdist] Question about local override > > CAUTION: This email is originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know the > content is safe. > > > Hi Rory, > > Does this help: > https://www.frank.be/implementing-bind-views-with-powerdns/ > > > Regards, > > Frank > > > Frank Louwers > PowerDNS Certified Consultant @ Kiwazo.be > >> On 10 May 2024, at 22:21, Rory Toma via dnsdist >> <dnsdist@mailman.powerdns.com> wrote: >> >> 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 lets say I have a domain view1.company.com that resolves normally. >> On my dnsdist server, I’d like to override this locally, and anyone >> that talks to that servers gets the overrides. What’s the best way to >> do this? >> thx >> _______________________________________________ >> dnsdist mailing list >> dnsdist@mailman.powerdns.com >> https://mailman.powerdns.com/mailman/listinfo/dnsdist > > _______________________________________________ dnsdist mailing list dnsdist@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/dnsdist
