You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Functions like setDNSSECPool, addDomainSpoof and addPoolRule can be mimicked with a 'normal' set of Rules and Actions. (e.g. setDNSSECPool == addAction(DNSSECRule(), poolAction())).
Forcing users to to be a little bit more explicit (using addAction, addResponseAction etc.) makes for a cleaner and better to understand configuration.
Usecase
Simplify initial understanding of how dnsdist's Rules and Actions hang together and ensure understandability of the configuration
The text was updated successfully, but these errors were encountered:
so I applaud this in theory, but we should document explicitly that addAction() accepts domain names, ip addresses and even lists of domain names and IP addresses as its first argument. It is (technically) documented now, but it appears in no example!
Short description
Right now there are multiple ways of accomplishing the same things in dnsdist. For instance
Functions like setDNSSECPool, addDomainSpoof and addPoolRule can be mimicked with a 'normal' set of Rules and Actions. (e.g.
setDNSSECPool
==addAction(DNSSECRule(), poolAction())
).Forcing users to to be a little bit more explicit (using addAction, addResponseAction etc.) makes for a cleaner and better to understand configuration.
Usecase
Simplify initial understanding of how dnsdist's Rules and Actions hang together and ensure understandability of the configuration
The text was updated successfully, but these errors were encountered: