Skip to content
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

DNS requests being received but not answered with a corrrect query response #83

Closed
DutchShadow opened this issue Mar 14, 2020 · 3 comments · Fixed by #84
Closed

DNS requests being received but not answered with a corrrect query response #83

DutchShadow opened this issue Mar 14, 2020 · 3 comments · Fixed by #84

Comments

@DutchShadow
Copy link

The DNS seeder runs and reports changes coming in on amount of DNS requests as well as having a lot of nodes found (.dump file checked and validated that it found good nodes) but it doesn't answer the requests properly.

@sipa
Copy link
Owner

sipa commented Mar 14, 2020

That's very little information to go on. Can you elaborate on "doesn't answer requests properly" ? What did you try, what do you expect to see, what do you see instead?

@DutchShadow
Copy link
Author

Thanks for the very quick response,
A dig command with a trace shows it finds the server but ends with a warming that the query response is not set

@DutchShadow
Copy link
Author

Seeder status:

Loading dnsseed.dat...done
Starting 4 DNS threads for eudns1.xxxx.net on dnsseed2.xxxx.com (port 53).......done
Starting seeder...done
Starting 96 crawler threads...done
[20-03-15 10:18:25] 1800/2716 available (2493 tried in 999s, 0 new, 223 active), 257 banned; 209 DNS requests, 4 db queries

End of a Dig with a +trace:

dnsseed2.xxxx.com. 300 IN      NS      eudns2.xxxx.net.
;; Received 89 bytes from 173.245.58.85#53(chloe.ns.cloudflare.com) in 13 ms

;; Warning: query response not set
;; Received 12 bytes from 81.2.x.207#53(eudns2.xxxx.net) in 35 ms

Digs increase the amount of DNS requests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants