Re: [dnsdist] DNS views using DNSDIST

[Jahanzeb Arshad via dnsdist]

Hi,

Thanks for your input. I tried the EDNS method but it doesnt seem to be
working for me. It also had a side effect of reducing the caching
performance of dnsdist from 80% to 20%, and also slightly increased the
CPU usage.

Tried the following method of replying with the SpoofAction. This seems
to be working in test environment. Am going to put it into production
and test.


match_clients_network = newNMG()
match_clients_network:addMask("192.168.122.1/32")

addAction(AndRule({NetmaskGroupRule(match_clients_network),
QNameRule('my.domain.com.'), QTypeRule(DNSQType.A)}),
SpoofAction("192.168.48.10"))

Regards

Jahanzeb


On Wed, 2021-01-27 at 10:33 +0100, frank+p...@tembo.be wrote:
> 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/ 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
> >  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 -> 192.168.10.10 for client IPs 10.10.10.0/24
> > web.domain.com -> 192.168.20.20 for client IPs 10.10.20.0/24
> > 
> > Regards
> > 
> > Jahanzeb
> > ___
> > dnsdist mailing list
> > 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

Re: [dnsdist] DNS views using DNSDIST

[frank+pdns--- via dnsdist]

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/ 
 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 
> 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    -> 192.168.10.10 for client IPs 
> 10.10.10.0/24
> web.domain.com    -> 192.168.20.20 for client IPs 
> 10.10.20.0/24
> 
> Regards
> 
> Jahanzeb
> ___
> dnsdist mailing list
> 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

[dnsdist] DNS views using DNSDIST

[Jahanzeb Arshad via dnsdist]

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 -> 192.168.10.10 for client IPs 10.10.10.0/24
web.domain.com -> 192.168.20.20 for client IPs 10.10.20.0/24

Regards

Jahanzeb
___
dnsdist mailing list
dnsdist@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/dnsdist