diff options
author | Lennart Poettering <lennart@poettering.net> | 2016-01-22 12:09:38 +0100 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2016-01-25 17:19:19 +0100 |
commit | 0791110fbee9d7dfcabd6e338c290e90aeb79644 (patch) | |
tree | 65b6d98ee572f7119a5176880630d280f13d2a82 /src/test/test-date.c | |
parent | 7bb70b6e3d6600d4c448c016b71073706460a12e (diff) |
resolved: properly handle LLMNR/TCP connection errors
The LLMNR spec suggests to do do reverse address lookups by doing direct LLMNR/TCP connections to the indicated
address, instead of doing any LLMNR multicast queries. When we do this and the peer doesn't actually implement LLMNR
this will result in a TCP connection error, which we need to handle. In contrast to most LLMNR lookups this will give
us a quick response on whether we can find a suitable name. Report this as new transaction state, since this should
mostly be treated like an NXDOMAIN rcode, except that it's not one.
Diffstat (limited to 'src/test/test-date.c')
0 files changed, 0 insertions, 0 deletions