Scott Mitchell fe5c69bdd9 DnsNameResolverContext#followCname only uses first name server ... Motivation: When following a CNAME it is possible there are multiple name servers to query against. However DnsNameResolverContext#followCname explicitly only uses the first name server address when attempting the query. This may lead to resolution failures because we didn't try all the available name servers. Modifications: DnsNameResolverContext#followCname should not just try the first name server, but it should try all name servers Result: More complete CNAME resolution.		2018-02-01 09:31:07 +01:00
..
DefaultDnsCacheTest.java	DefaultDnsCache should expire all records per hostname when one TTL is reached.	2018-01-31 14:39:31 +01:00
DnsNameResolverClientSubnetTest.java	DNS Resovler tests should be more explicit about ndots	2017-07-12 15:49:45 -07:00
DnsNameResolverTest.java	DnsNameResolverContext#followCname only uses first name server	2018-02-01 09:31:07 +01:00
DnsServerAddressesTest.java	DNS move JDK DNS resolution out of DnsServerAddresses static initialization	2017-04-06 18:09:58 -07:00
SearchDomainTest.java	Fix DN resolution when ndots is greater than 1	2017-11-20 14:01:16 +01:00
TestDnsServer.java	Prefer JDK ThreadLocalRandom implementation over ours.	2017-02-16 15:44:00 -08:00
UnixResolverDnsServerAddressStreamProviderTest.java	UnixResolverDnsServerAddressStreamProvider should allow for empty /etc/resolver dir	2017-07-05 20:14:27 -04:00