the second parameter to resolve() callback function
is request (kres.request_t), so the caller can
look into request stats, timing and zone cut data
:param number qtype: Query type (e.g. ``kres.type.NS``)
:param number qclass: Query class *(optional)* (e.g. ``kres.class.IN``)
:param number options: Resolution options (see query flags)
- :param function callback: Callback to be executed when resolution completes (e.g. `function cb (pkt) end`). The callback gets a packet containing the final answer and doesn't have to return anything.
+ :param function callback: Callback to be executed when resolution completes (e.g. `function cb (pkt, req) end`). The callback gets a packet containing the final answer and doesn't have to return anything.
:return: boolean
Example:
-- Query for AAAA record
resolve('example.com', kres.type.AAAA, kres.class.IN, 0,
- function (answer)
+ function (answer, req)
-- Check answer RCODE
local pkt = kres.pkt_t(answer)
if pkt:rcode() == kres.rcode.NOERROR then
lua_rawgeti(L, LUA_REGISTRYINDEX, cb_ref);
luaL_unref(L, LUA_REGISTRYINDEX, cb_ref);
lua_pushlightuserdata(L, req->answer);
- (void) execute_callback(L, 1);
+ lua_pushlightuserdata(L, req);
+ (void) execute_callback(L, 2);
}
static int wrk_resolve(lua_State *L)