Hi,
I'm trying to implement DNS64 in Unbound (the code by Viagenie sort of
works, but has a few issues and is pretty intrusive) and it looks to me
like a python/lua module would be a good idea to do it. This means that
I have to do a DNS query from within the module. What is the best way to
do it? I haven't seen any function to do that, can I just use
getaddrinfo() or python-dns?
Also, how much concurrency does the python module handle? The A query
might take some time during which the code will hang.
Or, even better, has someone already tried this?
Bernhard
I'm trying to implement DNS64 in Unbound (the code by Viagenie sort of
works, but has a few issues and is pretty intrusive)
What are the issues?
I was wondering if I should include the patch in the Fedora/rhel version of
unbound, so any stability issue you see (esp. when not using the nat64 options)
would be very useful to know.
Wouter: will this patch be merged into unbound?
(for those wondering see: Ecdysis: open-source nat64)
and it looks to me
like a python/lua module would be a good idea to do it. This means that
Wouldn't that be pretty bad for performance?
Paul
Hi,
I'm trying to implement DNS64 in Unbound (the code by Viagenie sort of
works, but has a few issues and is pretty intrusive)
What are the issues?
Mostly portability (which would be better if it was in-tree), but also
some SERVFAIL situations. For example for IPv6 reverse lookups OUTSIDE
of the NAT64 prefix (so for your native path). The code synthesizes PTRs
for the NAT64 prefix, I guess it is broken at this point. IÄm going to
report that, but the slow release cycles of ecdysis makes it annoying.
and it looks to me
like a python/lua module would be a good idea to do it. This means that
Wouldn't that be pretty bad for performance?
Probably. I was looking for a proof of concept. Also there might be
other situations where you need to do a DNS lookup from the module.
Bernhard
...which won't let you download without providing them intrusive personal details. That kind or crap INFURIATES me... No thanks, I'll use the DNS64 in bind 9.8 instead.
Hi,
I'm trying to implement DNS64 in Unbound (the code by Viagenie sort of
works, but has a few issues and is pretty intrusive)
What are the issues?
I was wondering if I should include the patch in the Fedora/rhel version of
unbound, so any stability issue you see (esp. when not using the nat64
options)
would be very useful to know.
Wouter: will this patch be merged into unbound?
The patch is to be merged if good quality and useful for general
audience. So I do not know. The source contrib directory in the
tarball of unbound is useful for putting the patch meanwhile. Or if the
license is a little different. Or if there are multiple patch
contenders. I have simply not received patch(es) to put into the
unbound contrib (but people are working 
).
(for those wondering see: http://ecdysis.viagenie.ca/download.html)
and it looks to me
like a python/lua module would be a good idea to do it. This means that
Wouldn't that be pretty bad for performance?
It is possible to make queries from the python module by creating a new
query for unbound to process (attach_query), then the query state that
has the subquery attached will get woken up with an event when that
query finishes processing. Potentially the result is there as well.
You can access this API from python, but to understand it you need to
read the c header files, I think, or the doxygen documentation. Note
that for example the new query gets full processing, and that includes
processing by your python module.
Best regards,
Wouter