Replies: 2 comments
-
I started from scratch on a vagrant VM. I reinstalled Bind9. My node VM is : 192.68.50.180. I have a loadbalancer (metallb) 192.68.50.200 Here my file named.conf.local
My ingress hosts are : dev.ns.example.com,dev.example.com My external-dns pod's logs are
the only entry that is reaching my ingress-controler is ns.example.com, look like external-dns is not able to update my BIND server
I installed external-dns with this :
if I dont put the param : tsigAxfr, I'll obtain this error in the logs
and in bind9 logs I have this :
|
Beta Was this translation helpful? Give feedback.
-
@survivant I'm running bind in k8s in my test setup and use external-dns to create NS records. See example manifests here: https://github.com/k0da/k8gb/tree/edge/deploy/edge |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I need help to complete my BIND9 with Kubernetes setup. I'm on premise. I want to add a domain name for my cluster like
dev.clusterxxx.local
qa.clusterxxx.local
I try to follow that guide : https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/rfc2136.md
here my named.conf.local file
my file zone.clusterxxx.local
I have my ingress-controller here (10.1.34.55)
I installed external-dns using Helm
My Bind server is on the IP 10.1.34.14
In my journal logs, I found this
Here the logs of external-dns pod
Beta Was this translation helpful? Give feedback.
All reactions