Norman Maurer 1a53df1031 Detect truncated responses caused by EDNS0 and MTU miss-match (#9468) ... Motivation: It is possible that the user uses a too big EDNS0 setting for the MTU and so we may receive a truncated datagram packet. In this case we should try to detect this and retry via TCP if possible Modifications: - Fix detecting of incomplete records - Mark response as truncated if we did not consume the whole packet - Add unit test Result: Fixes https://github.com/netty/netty/issues/9365		2019-08-17 09:58:40 +02:00
..
DefaultAuthoritativeDnsServerCacheTest.java	migrate java8: use lambda and method reference (#8781)	2019-01-29 14:06:05 +01:00
DefaultDnsCacheTest.java	migrate java8: use lambda and method reference (#8781)	2019-01-29 14:06:05 +01:00
DefaultDnsCnameCacheTest.java	migrate java8: use lambda and method reference (#8781)	2019-01-29 14:06:05 +01:00
DnsNameResolverClientSubnetTest.java	remove unused import statement (#8792)	2019-01-28 16:50:15 +01:00
DnsNameResolverTest.java	Detect truncated responses caused by EDNS0 and MTU miss-match (#9468)	2019-08-17 09:58:40 +02:00
DnsServerAddressesTest.java	Java 8 migration: Use diamond operator (#8749)	2019-01-22 16:07:26 +01:00
NameServerComparatorTest.java	Java 8 migration: Use diamond operator (#8749)	2019-01-22 16:07:26 +01:00
PreferredAddressTypeComparatorTest.java	DnsNameResolver.resolveAll(...) should also contain non preferred addresses (#9044)	2019-04-15 10:33:04 +02:00
SearchDomainTest.java	migrate java8 (#8779)	2019-01-28 05:55:30 +01:00
TestDnsServer.java	DnsNameResolver should log in trace level if notification of the promise fails (#9022)	2019-04-10 07:14:18 +02:00
UnixResolverDnsServerAddressStreamProviderTest.java	Correctly parse /etc/resolv.conf when contain multiple entries for searchdomain. (#8351)	2018-10-12 05:00:32 +02:00