6cd086050f
Motivation: The DNS resolver supports search domains. However the ndots are not correctly enforced. The search domain should only be appended under the following scenario [1]: > Resolver queries having fewer than ndots dots (default is 1) in them will be attempted using each component of the search path in turn until a match is found. The DNS resolver current appends the search domains if ndots is 0 which should never happen (because no domain can have less than 0 dots). [1] https://linux.die.net/man/5/resolv.conf Modifications: - Parse /etc/resolv.conf to get the default value for ndots on Unix platforms - The search domain shouldn't be used if ndots is 0 - Avoid failing a promise to trigger the search domain queries in DnsNameResolverContext#resolve Result: More correct usage of search domains in the DNS resolver. Fixes https://github.com/netty/netty/issues/6844.
Netty Project
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
Links
How to build
For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.
You require the following to build Netty:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.
Branches to look
Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.