Open CodeMonkeyKevin opened 10 years ago
NAPTR is broken in the current library. I'll merge the okTurtles fork in soon (today am traveling all day). You can use it in the meantime, it should work there.
Any chance on merging this in?
@CodeMonkeyKevin Yes, sorry, I was at a conference and now am back. My plan is to merge that in soon, maybe today or if not then this week. Can you confirm that the issue is fixed in that fork?
@CodeMonkeyKevin Sorry about not getting to merge the PR yet. I haven't forgotten and it's high up on my priority list, it's just competing with other slightly more high priority items. Were you able to check if the fork fixes your issue?
Sorry for the delay. It did not fix the issue, NAPTR queries still have the timeout issue.
When doing NAPTR query. All queries get timed out but tcpdump shows the server responded correctly and successfully to the query.
TCPDUMP, node-dns reported timeout but server sent back successful response before timeout window: 08:04:19.612311 IP 192.168.1.120.53110 > 192.168.1.90.53: 2407+ NAPTR? 3.3.2.2.1.1.5.5.5.5.1.e164enum.net. (52) 08:04:19.670588 IP 192.168.1.90.53 > 192.168.1.120.53110: 2407*- 1/1/0 NAPTR (200)
Doing the same query with dig shows same response and packet but without timeout.