[Plugin redis] issues with CNAME SOA and ? #6348
Unanswered
Underknowledge
asked this question in
Q&A
Replies: 1 comment
-
https://github.com/codysnider/coredns-redis isn't maintained by the coredns org. You might try reaching out to the maintainers of that project. |
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, now I'm bit sad.
Had the fun idea to setup an DNS, you know the typical stuff you do on a Saturday evening. here I am after 3 days.
But one where I dont have to write the same files to multiple servers, it should be cool!
Seccondary and forward ar'nt too nice as when you loose your primary, nothing can survive a reboot.
Oh, I can use redis? nice!
well after figuring everything out I can proudly state, it is broken (could be me thou)
Documentation:
what I have:
Querying SOA is fun
Cname is "fun" too. not usable with webservers and what not
When I use a config file, everything works as expected.
So I think that's the plugins fault (or I'm a idiot, proved that many times already)
When you want to give it a try, be my guest! stuff is Here
more or less, install redis, copy the config file .configfiles/redis/redis.conf into /etc/redis/redis.conf
when you started it, add some records to redis.
download the go script from here
and add some records to arpa.corp like This
download Coredns with the redis plug-in enabled from here and use it with
.configfiles/coredns/Corefile
TLDR:
Redis behaves wired. CNAME'S dont get expanded, SOA gives bad packets back.
idk what's going on, but I might think there is an issue with the redis plugin.
when you have ideas on how to get this to working, plzzz. would be sad when this have been a waste of time.
Beta Was this translation helpful? Give feedback.
All reactions