New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hosts with DNS suffixes cannot be resolved in Windows 10 and Java 9+ #12712
Comments
flupec
changed the title
DNS suffixes cannot be resolved in Windows 10 and Java 9+
Hosts with DNS suffixes cannot be resolved in Windows 10 and Java 9+
Aug 18, 2022
@flupec the problem is that this is a "private" api that you can only access via reflection which will fail in java9+ or at least produce an error log. So there is not much we can do about it . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using Spring WebClient based on netty and it cannot resolve hosts with DNS suffixes on Windows and Java 9+. I think this hack is responsible for such behaviour.
Why is reflection used here? You can acquire instance of ResolverConfiguration via static method, no?
Java 8 works fine though. I think issue is simillar to this.
Expected behavior
Hosts with dns suffixes resolves succesfully
Actual behavior
UnknownHostException
Steps to reproduce
Configure DNS suffixes on Windows. This can be achieved like this: edit SearchList property at registry path HKLM\SYSTEM\CurrentControlSet\services\Tcpip\Parameters.
Netty version
4.1.77.Final
JVM version (e.g.
java -version
)OS version (e.g.
uname -a
)Windows 10
The text was updated successfully, but these errors were encountered: