LUA zone apex setup issues #13231
Unanswered
joachimtingvold
asked this question in
Q&A
Replies: 2 comments 3 replies
-
Please read #13200 and update your post, thanks! |
Beta Was this translation helpful? Give feedback.
1 reply
-
DO means 'DNSSEC OK'. I do not have another explanation for the failure, however. Are you sure the configuration is identical? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I attempted to implement the workaround LUA zone apex setup mentioned in #3838, and followed the example here, but I'm having a hard time getting it to work.
Setup consists of three servers;
enable-lua-records=yes
is set on all three servers. I can query for theLUA
record onauthdns-master
just fine;If I enable debug on
authdns-master
, I see the following;However, if I attempt to do this on
authdns1
orauthdns2
, I don't get the desired response;If I enable logging on
authdns1
, I only see the following when doing two lookups in a row;If I look in the database for
authdns1
andauthdns2
(PostgreSQL backend), I can see theLUA
records just fine. They are identical to the ones stored in theauthdns-master
database:I initially thought it could be related to not having set the
resolver
configuration parameter. However, it seems like it picks the system resolvers if it's unset (which is also evident from the logs onauthdns-master
above, which was done without havingresolver
set). I can also see during the startup onauthdns1
andauthdns2
that resolver is working fine;Anyone have any ideas why this might not be working?
I also notice that the logs has
do = 1
onauthdns-master
versus thedo = 0
on theauthdns1
. Not sure what thedo
flag means?Version/build-configuration is equal on all servers;
Beta Was this translation helpful? Give feedback.
All reactions