[dnsdist] Dnsdist dynamic backend selection between AUTH and RECURSOR

[Otto Moerbeek]

Hi,

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. If that is not feasible, take a look at

https://dnsdist.org/reference/kvs.html

Have a process update the kv-database and dnsdist can use that to make
its decisions.

	-Otto
	

On Sat, Jan 07, 2023 at 10:14:17AM +0100, bernd--- via dnsdist wrote:

> Hello!
> 
>  
> 
> I have a question regarding the architecture of DNSDIST in front of an
> authorative pdns instance as well as an recursor.
> 
> I`ve looked at: https://doc.powerdns.com/authoritative/guides/recursion.html
> - however, the solutions described are kind of static.
> 
> Eg. Domains send to the auth-instance have to be specified manually in the
> config.
> 
>  
> 
> What I love to achieve is:
> 
>  
> 
> Let DNSDIST dynamicly select if a Request should be send to AUTH or
> RECURSOR.
> 
> For Latency, the list of AUTH-Domains should be somehow synced locally to
> the DNSDIST-Instance itself.
> 
> DNSDIST should not ask AUTH always and if it fails forward the request to
> the Recursor.
> 
> Also if another Domain is added to the AUTH-Instance, this domain should be
> added to the DNSDIST Config.
> 
>  
> 
> I tought about getting the Domain List via API on Startup and adding new
> records via Control-Socket.
> 
>  
> 
> Has someone done a similar thing already?
> 
>  
> 
> PS: Sorry for some potential false spellings - i`m not native.
> 
>  
> 
> BR
> 
> Bernd
> 
> https://berndklaus.at
> 
>  
> 

> _______________________________________________
> dnsdist mailing list
> dnsdist at mailman.powerdns.com
> https://mailman.powerdns.com/mailman/listinfo/dnsdist