Differences

This shows you the differences between two versions of the page.

Link to this comparison view

irc:1485126000 [2017/05/27 13:44] (current)
Line 1: Line 1:
 +[19:42:16] <​BadApe>​ hi, i've got a very strange error message, when trying to make an http connection 2017-01-23 18:40:13 SEVERE io.vertx.core.http.impl.HttpClientRequestImpl java.net.UnknownHostException:​ failed to resolve '​api.steampowered.com'​. Exceeded max queries per resolve 3
 +
 +[19:42:40] <​BadApe>​ yes maybe my dns is not working, however nslookup can get the ip address and so can the vertx dns client
 +
 +[19:43:38] <​AlexLehm>​ BadApe: hi, i meant to answer the question yesterday but I missed you
 +
 +[19:44:03] <​AlexLehm>​ are you using vert.x 3.4.0-SNAPSHOT?​
 +
 +[19:44:05] <​BadApe>​ oh thanks,
 +
 +[19:44:10] <​BadApe>​ i am using 3.3.3
 +
 +[19:44:28] <​BadApe>​ i am not brave enough to use cutting edge
 +
 +[19:44:41] <​AlexLehm>​ there is an issue in the dns resolver from netty that causes problems when resolving addresses with CNAMES
 +
 +[19:45:09] <​AlexLehm>​ I think that it only happending in 3.4 with netty 4.1.6, but maybe it happens in some cases with 3.3.3 and netty 4.1.5 as well
 +
 +[19:45:54] <​BadApe>​ what is odd is that it '​used'​ to work
 +
 +[19:46:43] <​AlexLehm>​ ok, maybe its related to the dns server
 +
 +[19:47:12] <​AlexLehm>​ I will set up a test project with 3.3.3 to check if it happens generally with the hostname
 +
 +[19:48:03] <​BadApe>​ well i thought maybe my dns server had problems
 +
 +[19:48:27] <​BadApe>​ so my laptop has gone from home, to work to this hotel room
 +
 +[19:50:06] <​AlexLehm>​ maybe
 +
 +[19:54:07] <​AlexLehm>​ ok, the request works on my machine, so i am wrong with the cause of the issuse
 +
 +[19:55:45] <​BadApe>​ i just checked that i have 4.1.5
 +
 +[19:56:05] <​BadApe>​ so nothing by magic upgraded netty
 +
 +[19:57:10] <​AlexLehm>​ ok, i can reproduce the issue with 3.4.0-snapshot,​ but it doesn'​t happen on 3.3.3
 +
 +[19:58:06] <​AlexLehm>​ ok, then i was wrong about the issue i cannot say why it happens on 3.3.3 for you
 +
 +[19:59:28] <​BadApe>​ thanks for helping
 +
 +[20:01:47] <​BadApe>​ can't even resolve with the http client using an A name entry
 +
 +[20:41:59] <​AlexLehm>​ maybe it chooses the wrong dns server, you can probably configure the dnsclient to use one explicitly
 +
 +[20:48:50] <​BadApe>​ http://​pastie.org/​10992046
 +
 +[20:49:11] <​BadApe>​ i downgraded to 3.3.2 and got more interesting logging
 +
 +[20:49:25] <​BadApe>​ this time i just tried to resolve www.google.com
 +
 +[21:02:22] <​AlexLehm>​ maybe the ip for the resolver is wrong, 192.168.4.1 ?
 +
 +[21:03:36] <​BadApe>​ yes that is totally wrong
 +
 +[21:03:46] <​BadApe>​ weirdly enough i can't see where it is getting that wrong
 +
 +[21:04:35] <​BadApe>​ maybe docker screwing things up
 +
 +[21:07:01] <​AlexLehm>​ if its inside docker, the address may be correct as a local resolver
 +
 +[21:07:32] <​AlexLehm>​ my docker knowlege is almost non-existent,​ could you to use the resolver that you have on the local machine?
 +
 +[21:07:45] <​AlexLehm>​ try to use
 +
 +[21:09:03] <​BadApe>​ it is out side docker
 +
 +[21:09:28] <​BadApe>​ well the hotel is giving the machine google'​s 8.8.8.8
 +
 +[21:09:50] <​BadApe>​ i think it must be a weird windows problem because i can't see where it is getting this 192.168 dns servers from
 +
 +[21:09:59] <​BadApe>​ the hotel'​s subnet is 10.x
 +
 +[21:10:49] <​BadApe>​ AlexLehm, what version jdk are you using?
 +
 +[21:55:08] <​BadApe>​ AlexLehm, it was my laptop being rubbish, some bundle ware was screwing with the dns servers