Start planning service to integrate into NextDNS and Adguard.

[jaypatrick]

It needs to be extensible so other DNS services can be added via code or configuration, or both.

The goal is to compile blocklists, then use AdguardDNS/NextDNS APIs to upload custom blocklists.

Should there be a separate service? Generate an API client? What should the architecture be?

[github-actions]

The GitHub issue proposes planning a service to integrate with NextDNS and AdguardDNS for uploading custom blocklists. The service should be extensible, allowing additional DNS services to be incorporated through code or configuration. Key considerations include whether the functionality should be handled by a separate service, the potential need for generating an API client, and deciding on the optimal architecture for implementing the solution. The ultimate goal is to compile blocklists and use the APIs of AdguardDNS and NextDNS to upload these lists seamlessly.

[jaypatrick]

Maybe this should be a separate service written in C#?