[dnsdist] Dnsdist dynamic backend selection between AUTH and RECURSOR

[bernd at klaus.onl]

Hello!

I am aware that the solution I am aiming for is not the optimum.

However, I use fly.io as a platform where I have already distributed DNSDIST containers to over 20 locations with Anycast IP.
The problem comes with the limitations of the fly - one app is bound to a set of IPs. You can not distinguish within the app between different IPs on the same app.
This means, I would have to start another 20 Instances of dnsdist.... 

May I can code an Pub/Sub solution or make use of the KV Store... I still have to think my way into it.

If someone is interested in my fly.io solution (Alpha State, testing only, no warranty!):

https://github.com/Berndinox/flyio-powerdns-dnsdist
https://github.com/Berndinox/flyio-powerdns-pg


BR
Bernd


-----Ursprüngliche Nachricht-----
Von: Chris Hofstaedtler | Deduktiva <chris.hofstaedtler at deduktiva.com> 
Gesendet: Samstag, 7. Januar 2023 12:50
An: Bernd KLAUS <bernd at klaus.onl>
Cc: dnsdist at mailman.powerdns.com
Betreff: Re: [dnsdist] Dnsdist dynamic backend selection between AUTH and RECURSOR

Hello Bernd,

* Bernd KLAUS via dnsdist <dnsdist at mailman.powerdns.com> [230107 11:01]:
> Regarding:
> „ My first suggestion would be to not need to do the name based 
> forwarding by separating the incoming recurosr and auth traffic on ip 
> address or port“
> 
> So i should forward all querys to the recursor?

I believe the best practice is to have a dedicated IP for auth services, and another dedicated IP for recursive.

I'd expect Otto's suggestions to be that ^.

Best,
--
Chris Hofstaedtler / Deduktiva GmbH (FN 418592 b, HG Wien) www.deduktiva.com / +43 1 353 1707