- Aug 24, 2016
-
-
Ondřej Surý authored
timeouts over TCP when <n> first nameservers timeout over UDP as previously the TCP would connect again to the first and only the first nameserver in task->addrlist. This would need to be ultimately fixed in TCP Fast Retransmit.
-
- Aug 11, 2016
-
-
-
-
-
-
-
-
-
-
The control structure is part of the resolver context.
-
-
-
-
-
Use ENABLE_cookies=yes variable to compile functionality.
-
-
Cookies are not stored in separate cache.
-
-
-
-
-
-
- Aug 05, 2016
-
-
Ondřej Surý authored
-
Ondřej Surý authored
-
Ondřej Surý authored
-
Ondřej Surý authored
-
the TLS sessions now bypass the usuall event loop asynchronous iops this is because the whole operation is synchronous right now, and implementing asynchronous send operations would require TLS session to restart write events on the event loop and making sure the "on complete" callback is called eventually
-
-
- Jul 16, 2016
-
-
Daniel Kahn Gillmor authored
-
- Jul 06, 2016
-
-
Marek Vavrusa authored
the e638f9fb introduced deduplication for queries over UDP, the idea is to track same queries and answer only once, however that introduces both constant processing and memory overhead and could break clients who count packet loss by queries sent/received. disabling for now.
-
Marek Vavrusa authored
* in the begin() layer, the incoming query is exposed as req->qsource.packet, it is invalidated after begin() and should not be modified * the destination address (local interface) is also tracked for filtering purposes
-
- Jun 16, 2016
-
-
Marek Vavrusa authored
previously the buffer for TCP pkt reassembly was not correctly cleared and fragmented answers were rejected
-
Marek Vavrusa authored
-
- May 22, 2016
-
-
Marek Vavrusa authored
* when enqueued task terminated earlier than leader task because of timeout, it wasn't dequeued from the waitlist immediately, but it didn't have any outstanding outbound queries. when leader task terminated, it removed this task and updated its outbound query, which didn't exist. this triggered a 16B write in undefined location * fixed timeout timer being scheduled for closing without holding reference to parent task
-
- May 15, 2016
-
-
Marek Vavrusa authored
-
- May 12, 2016
-
-
Marek Vavrusa authored
many clients do frequent retransmits of the query to avoid network losses and get better service, but then fail to work properly when a resolver answers SERVFAIL to some of them because of the time limit and some of them NOERROR. it's also a good idea to avoid wasting time tracking pending tasks to solve the same thing.
-
- May 11, 2016
-
-
Marek Vavrusa authored
if the upstream TCP query timeouted or the connection was severed, it would dissociate the handle from original query, so the query would be solved but the requestor wouldn't see the answer unless he requeried
-
Marek Vavrusa authored
-
Marek Vavrusa authored
-
- May 06, 2016
-
-