Hi, You would have a few options to do that.
I wrote a blogpost about implementing BIND views using dnsdist and two instances of powerdns-auth. See https://www.frank.be/implementing-bind-views-with-powerdns/ <https://www.frank.be/implementing-bind-views-with-powerdns/> for details. If you want to keep a single BIND as a backend, you could investigate EDNS client subnet support. There are other options, but the two above would my preferred way... Kind Regards, Frank > On 27 Jan 2021, at 10:23, Jahanzeb Arshad via dnsdist > <dnsdist@mailman.powerdns.com <mailto:dnsdist@mailman.powerdns.com>> wrote: > > Greetings, > > We have been using BIND DNS server with views to return different A records > for different source networks. Now we have put DNSDIST as frontend to the > BIND DNS servers. Now BIND DNS is seeing the dnsdist as the client IP and the > views are no more valid. We are unable to figure out how we can we create > same type of views on the dnsdist application. Any help would be appreciated. > > For example following different A records to be returned for different client > IPs for a specific application/domain name. > > web.domain.com <http://web.domain.com/> -> 192.168.10.10 for client IPs > 10.10.10.0/24 > web.domain.com <http://web.domain.com/> -> 192.168.20.20 for client IPs > 10.10.20.0/24 > > Regards > > Jahanzeb > _______________________________________________ > dnsdist mailing list > dnsdist@mailman.powerdns.com <mailto:dnsdist@mailman.powerdns.com> > https://mailman.powerdns.com/mailman/listinfo/dnsdist Frank Louwers PowerDNS Certified Consultant @ Kiwazo.be
_______________________________________________ dnsdist mailing list dnsdist@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/dnsdist
