This page is more of a ‘note to self’ than anything else really. The ideas on this page are subject to change and depend on my personal resources, i.e. my spare time and funds.

  • Implement IPv6

    Current status: On hold
    Reason: By default, the Docker daemon configures the container’s network for IPv4 only. Additional steps are needed to enable IPv4/IPv6 dualstack support.
    However, Scaleway’s implementation of IPv6 is not ideal. All Pi-holes run on a Virtual Private Server (VPS), i.e. multiple virtual servers reside on the same physical machine. Scaleway only provides IPv6 tied to the physical server, meaning that your IPv6 will change if you stop/migrate/rebuild your server…
    More information regarding this issue can be found here.

  • Implement Anycast IP with Loadbalancer

    Current status: On hold
    Reason: I already explored the option of using Scaleway’s and OVH’s ‘cloud loadblancer’, but both do not support UDP at this time. This is a hard requirement, since DNS needs both UDP and TCP.

  • Deploy Pi-holes to Kubernetes cluster

    Current status: Exploratory phase
    Reason: The current resources are more than enough to handle the current load. Should the load increase dramatically, it might be feasible to deploy the Pi-holes to a Kubernetes cluster so that the resources can scale dynamically instead of overestimating resources. Some providers offer ‘managed’ Kubernetes clusters. Depending on their price that might be an option.