Replies: 1 comment
-
I personally don't like the idea of creating an API for this as it's essentially dynamic DNS which is standard. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all 😃
my gut feeeling tells me this is something that has been discussed somewhere before, but I didn't find it, so here it goes
In my homelab I was running blocky as an adblocker and internal dns server. It just works, no more complex than needed, but neither simpler. I like that 👍
But when I started using
external-dns
to get my ingresses fqdn's availables from the network automatically, I realized there was not a blocky provider. I tried to figure out an out of the box approach to make it work (updating the config and reload the config, for example?). I think a dedicated API Endpoint to manage the custom dns records can be useful in a number of situations, but in particular to write an external-dns provider.Does this sound useful for someone else?
Regards
Beta Was this translation helpful? Give feedback.
All reactions