ExternalDNS webhook for Hostinger DNS. Makes Kubernetes keep your Hostinger DNS records up to date.
341
Make Kubernetes keep your Hostinger DNS records up to date, all by itself.
This image is a webhook provider for ExternalDNS. It runs next to external-dns, in the same pod, and turns its requests into calls to the Hostinger API. Add a hostname to a Service or Ingress, and the record appears in your Hostinger DNS zone. Delete it, and the record goes away.
Create an API token in hPanel (Profile > API) with an expiry date. A Hostinger token can do everything your account can do, so keep it secret.
kubectl create namespace external-dns
kubectl -n external-dns create secret generic hostinger-credentials \
--from-literal=api-token='...'
curl -LO https://raw.githubusercontent.com/hayone1/external-dns-hostinger-webhook/main/deploy/helm/values.yaml
# edit values.yaml: set your domain, cluster name and image tag
helm repo add external-dns https://kubernetes-sigs.github.io/external-dns/
helm upgrade --install external-dns external-dns/external-dns \
--namespace external-dns -f values.yaml
Your domain must use Hostinger's name servers (ns1.dns-parking.com and
ns2.dns-parking.com).
X.Y.Z and vX.Y.Z - one exact release (use this in production)X.Y - the newest patch of a minor versionlatest - the newest release (not recommended for production)Platforms: linux/amd64, linux/arm64.
gcr.io/distroless/static: no shell, no package manager65532, works with a read-only root file systemPorts: 8888 (webhook API, localhost only by default), 8080 (/healthz,
/readyz, /metrics).
The same image is also on GitHub: ghcr.io/hayone1/external-dns-hostinger-webhook.
Apache License 2.0. Not made by or connected to Hostinger.
Content type
Image
Digest
sha256:0ed0b92a8…
Size
9.5 MB
Last updated
5 days ago
docker pull hayone/external-dns-hostinger-webhook