mapumbaa@lemmy.zip to Selfhosted@lemmy.worldEnglish · 1 年前How do you solve dynamic DNS?message-squaremessage-square59linkfedilinkarrow-up164arrow-down10file-text
arrow-up164arrow-down1message-squareHow do you solve dynamic DNS?mapumbaa@lemmy.zip to Selfhosted@lemmy.worldEnglish · 1 年前message-square59linkfedilinkfile-text
minus-squarephilthi@lemmy.worldlinkfedilinkEnglisharrow-up5·1 年前Have you heard of the kuadrant project? It is for kubernetes and has a dynamic DNS element. Kuadrant.io
minus-squaremapumbaa@lemmy.zipOPlinkfedilinkEnglisharrow-up4·1 年前Probably good, but I want to stay away from anything related to Kubernetes. My experience is that it’s an overkill black hole of constant debugging. Unfortunately. Thanks though!
minus-squareJustin@lemmy.jlh.namelinkfedilinkEnglisharrow-up1·1 年前Interesting, this seems to have better documentation and feedback than the external-dns operator
minus-squarephilthi@lemmy.worldlinkfedilinkEnglisharrow-up2·1 年前It leans on the external-dns operator in it’s DNS operator.
Have you heard of the kuadrant project? It is for kubernetes and has a dynamic DNS element. Kuadrant.io
Probably good, but I want to stay away from anything related to Kubernetes. My experience is that it’s an overkill black hole of constant debugging. Unfortunately. Thanks though!
Interesting, this seems to have better documentation and feedback than the external-dns operator
It leans on the external-dns operator in it’s DNS operator.
Ah, cool, interesting!